[Bug libgomp/66756] libgfortran: ThreadSanitizer: lock-order-inversion

2021-05-22 Thread xw111luoye at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66756 Ye Luo changed: What|Removed |Added CC||xw111luoye at gmail dot com --- Comment #18

[Bug libgomp/66756] libgfortran: ThreadSanitizer: lock-order-inversion

2017-12-06 Thread janus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66756 --- Comment #17 from janus at gcc dot gnu.org --- I tried configuring GCC with --enable-linux-futex=no, but that did not really solve the problem for me. Maybe I'm using that flag in a wrong way?

[Bug libgomp/66756] libgfortran: ThreadSanitizer: lock-order-inversion

2017-12-06 Thread janus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66756 --- Comment #16 from janus at gcc dot gnu.org --- (In reply to Thomas Koenig from comment #14) > Following the discussion at > > https://gcc.gnu.org/ml/fortran/2017-10/msg2.html > > all the false positives go away if --enable-linux-futex=no

[Bug libgomp/66756] libgfortran: ThreadSanitizer: lock-order-inversion

2017-10-01 Thread tkoenig at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66756 --- Comment #15 from Thomas Koenig --- *** Bug 82378 has been marked as a duplicate of this bug. ***

[Bug libgomp/66756] libgfortran: ThreadSanitizer: lock-order-inversion

2017-10-01 Thread tkoenig at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66756 Thomas Koenig changed: What|Removed |Added Status|ASSIGNED|NEW Last reconfirmed|2015-11-10