summaryrefslogtreecommitdiff
path: root/PCbuild
diff options
context:
space:
mode:
authorJeffrey Yasskin <jyasskin@gmail.com>2010-05-03 19:29:34 +0000
committerJeffrey Yasskin <jyasskin@gmail.com>2010-05-03 19:29:34 +0000
commit8cc1fda6b8c2d74a3abd2b8a007880656add8997 (patch)
tree98c8ddb5111deb4311ccc88f0a875790f3d6e667 /PCbuild
parent916fe4197d8172e967b7e25d93ac9660c45ab0ea (diff)
downloadcpython-8cc1fda6b8c2d74a3abd2b8a007880656add8997.tar.gz
Make (most of) Python's tests pass under Thread Sanitizer.
http://code.google.com/p/data-race-test/wiki/ThreadSanitizer is a dynamic data race detector that runs on top of valgrind. With this patch, the binaries at http://code.google.com/p/data-race-test/wiki/ThreadSanitizer#Binaries pass many but not all of the Python tests. All of regrtest still passes outside of tsan. I've implemented part of the C1x atomic types so that we can explicitly mark variables that are used across threads, and get defined behavior as compilers advance. I've added tsan's client header and implementation to the codebase in dynamic_annotations.{h,c} (docs at http://code.google.com/p/data-race-test/wiki/DynamicAnnotations). Unfortunately, I haven't been able to get helgrind and drd to give sensible error messages, even when I use their client annotations, so I'm not supporting them.
Diffstat (limited to 'PCbuild')
-rw-r--r--PCbuild/pythoncore.vcproj8
1 files changed, 8 insertions, 0 deletions
diff --git a/PCbuild/pythoncore.vcproj b/PCbuild/pythoncore.vcproj
index fde5cd1691..2388a71722 100644
--- a/PCbuild/pythoncore.vcproj
+++ b/PCbuild/pythoncore.vcproj
@@ -703,6 +703,10 @@
>
</File>
<File
+ RelativePath="..\Include\dynamic_annotations.h"
+ >
+ </File>
+ <File
RelativePath="..\Include\enumobject.h"
>
</File>
@@ -1660,6 +1664,10 @@
>
</File>
<File
+ RelativePath="..\Python\dynamic_annotations.c"
+ >
+ </File>
+ <File
RelativePath="..\Python\dynload_win.c"
>
</File>