This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libgomp/67303] libgomp: ThreadSanitizer: data race in libgomp


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67303

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
This is a partly false negative.  In the sense the load from ws->start just
needs to be __atomic_load(&ws->start, RELAX) to be correct.  This in it of
itself is the same as what it is correctly doing.  Just removes the error from
the thread santitizer.

The main reason why I say this is because we are doing a compare and swap loop
to check if ws->start has changed when doing the lock-less popping off the
stack.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]