You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Debugged some more. It's not actually a deadlock. It's just that that particular test hits the thread sanitizer performance penalty really hard. Adjusting the problem size gets it down to a reasonable runtime.
The
qarray
test hangs with thread sanitizer (x86-64, nemesis, clang17, no topology detection).Prior to hanging though, it also emits various thread sanitizer errors:
atomic write:
qthreads/src/ds/qarray.c
Line 738 in 619afe9
non-atomic read of same variable:
qthreads/src/ds/qarray.c
Line 1033 in 619afe9
In the test itself, non-atomic read:
qthreads/test/features/qarray.c
Line 110 in 619afe9
atomic write:
qthreads/test/features/qarray.c
Line 28 in 619afe9
Similar:
qthreads/test/features/qarray.c
Line 124 in 619afe9
qthreads/test/features/qarray.c
Line 27 in 619afe9
Similar:
qthreads/test/features/qarray.c
Line 90 in 619afe9
qthreads/test/features/qarray.c
Line 20 in 619afe9
Somewhat similar:
Non-atomic write:
qthreads/test/features/qarray.c
Line 104 in 619afe9
Atomic write:
qthreads/test/features/qarray.c
Line 21 in 619afe9
Non-atomic write:
qthreads/src/ds/qarray.c
Line 545 in 619afe9
Non-atomic read:
qthreads/src/ds/qarray.c
Line 706 in 619afe9
Note the read occurs inside the called function
qarray_elem_nomigrate
at:qthreads/include/qthread/qarray.h
Line 114 in 619afe9
Non-atomic write:
qthreads/src/ds/qarray.c
Line 982 in 619afe9
Atomic write to same address:
qthreads/src/ds/qarray.c
Line 738 in 619afe9
The text was updated successfully, but these errors were encountered: