This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libgomp/51298] libgomp team_barrier locking failures
- From: "amodra at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 15 Dec 2011 13:45:20 +0000
- Subject: [Bug libgomp/51298] libgomp team_barrier locking failures
- Auto-submitted: auto-generated
- References: <bug-51298-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51298
--- Comment #6 from Alan Modra <amodra at gmail dot com> 2011-12-15 13:45:20 UTC ---
I expect all of the libgomp bugs I recently fixed will affect some other
processors, eg. Alpha, IA64, and Sparc in some memory modes. I know PR51376
won't affect x86, and I expect PR51249 will affect all processors. Beyond
that, I haven't analyzed which bugs will affect a given processor. BTW,
there's a good article here http://www.linuxjournal.com/article/8211 that
explains how and why memory accesses are reordered, and the extent that various
processors do reordering. The table in that article is why I named Alpha, IA64
and Sparc.