This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug other/51124] libitm failures
- From: "dominiq at lps dot ens.fr" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 09 Jan 2012 10:23:06 +0000
- Subject: [Bug other/51124] libitm failures
- Auto-submitted: auto-generated
- References: <bug-51124-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51124
--- Comment #9 from Dominique d'Humieres <dominiq at lps dot ens.fr> 2012-01-09 10:23:06 UTC ---
libitm.c/memcpy-1.c and memset-1.c are still failing in 32 bit mode on
*86*-*-*. From
http://glutton.geoffk.org/HEAD/native-logsum/i686-pc-linux-gnu/libitm/testsuite/libitm.log.gzip
, the failure is
libitm: pr_undoLogCode not supported
FAIL: libitm.c/memcpy-1.c execution test
I also see that on x86_64-apple-darwin10. This comes from line 163 of
libitm/beginend.cc
// ??? pr_undoLogCode is not properly defined in the ABI. Are barriers
// omitted because they are not necessary (e.g., a transaction on thread-
// local data) or because the compiler thinks that some kind of global
// synchronization might perform better?
if (unlikely(prop & pr_undoLogCode))
GTM_fatal("pr_undoLogCode not supported");