diff options
| author | Dmitry Vyukov <dvyukov@google.com> | 2016-04-27 12:30:48 +0000 |
|---|---|---|
| committer | Dmitry Vyukov <dvyukov@google.com> | 2016-04-27 12:30:48 +0000 |
| commit | 3efe395788e17f9be556b2570fb0cd9a1ae93796 (patch) | |
| tree | e1e706b5b00c4b4018cd55b67b41a8739f702db8 /lldb/packages/Python/lldbsuite/test/lang/cpp/this/TestCPPThis.py | |
| parent | 15cec298e64872b693430214980a822ee2044a5d (diff) | |
| download | bcm5719-llvm-3efe395788e17f9be556b2570fb0cd9a1ae93796.tar.gz bcm5719-llvm-3efe395788e17f9be556b2570fb0cd9a1ae93796.zip | |
tsan: change tsan/Go interface for obtaining the current Processor
Current interface assumes that Go calls ProcWire/ProcUnwire
to establish the association between thread and proc.
With the wisdom of hindsight, this interface does not work
very well. I had to sprinkle Go scheduler with wire/unwire
calls, and any mistake leads to hard to debug crashes.
This is not something one wants to maintian.
Fortunately, there is a simpler solution. We can ask Go
runtime as to what is the current Processor, and that
question is very easy to answer on Go side.
Switch to such interface.
llvm-svn: 267703
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/lang/cpp/this/TestCPPThis.py')
0 files changed, 0 insertions, 0 deletions
