| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
llvm-svn: 371687
|
|
|
|
|
|
|
|
|
|
|
|
| |
Objects may move during the garbage collection, and JVM needs
to notify ThreadAnalyzer about that. The new function
__tsan_java_find eliminates the need to maintain these
objects both in ThreadAnalyzer and JVM.
Author: Alexander Smundak (asmundak)
Reviewed in https://reviews.llvm.org/D27720
llvm-svn: 289682
|
|
|
|
|
|
| |
They are meaningless.
llvm-svn: 240539
|
|
|
|
|
|
| |
This is required for Java support, as real PCs don't work for Java.
llvm-svn: 236484
|
|
|
|
|
|
|
|
| |
Even sleep(1) lead to episodical flakes on some machines.
Use an invisible by tsan barrier to enforce required execution order instead.
This makes the tests deterministic and faster.
llvm-svn: 226659
|
|
|
|
|
|
| |
they are required to handle synchronization on volatile/final fields
llvm-svn: 224697
|
|
|
|
|
|
|
| |
It is required to prevent false positives between object ctor and finalizer,
as otherwise they look completely unsynchronized.
llvm-svn: 211829
|
|
llvm-svn: 201414
|