This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Libitm issues porting to POWER8 HTM
- From: Andi Kleen <andi at firstfloor dot org>
- To: Peter Bergner <bergner at vnet dot ibm dot com>
- Cc: "gcc\ at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>, Andreas Krebbel <krebbel at linux dot ibm dot com>
- Date: Tue, 18 Jun 2013 11:22:58 -0700
- Subject: Re: Libitm issues porting to POWER8 HTM
- References: <1371257094 dot 1396 dot 189 dot camel at otta>
Peter Bergner <bergner@vnet.ibm.com> writes:
>
> I have yet to track down who has the write lock and why, but I am working
> towards that. Talking with Andreas, he said he is seeing the same failure
> on S390, so I'm wondering whether this might be a generic libitm issue
> and it might hit Intel too. Does anyone know whether this executes correctly
> on Intel hardware with RTM? I'll note that if I hack the call to
FWIW on a TSX system I get the following for libitm with current
trunk. So no hangs on reentrant at least.
Native configuration is x86_64-unknown-linux-gnu
=== libitm tests ===
Schedule of variations:
unix
Running target unix
Running /home/ak/gcc/gcc/libitm/testsuite/libitm.c/c.exp ...
PASS: libitm.c/cancel.c (test for excess errors)
PASS: libitm.c/cancel.c execution test
PASS: libitm.c/clone-1.c (test for excess errors)
PASS: libitm.c/clone-1.c execution test
PASS: libitm.c/dropref-2.c (test for excess errors)
XFAIL: libitm.c/dropref-2.c execution test
PASS: libitm.c/dropref.c (test for excess errors)
XFAIL: libitm.c/dropref.c execution test
PASS: libitm.c/memcpy-1.c (test for excess errors)
PASS: libitm.c/memcpy-1.c execution test
PASS: libitm.c/memset-1.c (test for excess errors)
PASS: libitm.c/memset-1.c execution test
PASS: libitm.c/notx.c (test for excess errors)
PASS: libitm.c/notx.c execution test
PASS: libitm.c/reentrant.c (test for excess errors)
PASS: libitm.c/reentrant.c execution test
PASS: libitm.c/simple-1.c (test for excess errors)
PASS: libitm.c/simple-1.c execution test
PASS: libitm.c/simple-2.c (test for excess errors)
PASS: libitm.c/simple-2.c execution test
PASS: libitm.c/stackundo.c (test for excess errors)
PASS: libitm.c/stackundo.c execution test
PASS: libitm.c/txrelease.c (test for excess errors)
PASS: libitm.c/txrelease.c execution test
Running /home/ak/gcc/gcc/libitm/testsuite/libitm.c++/c++.exp ...
PASS: libitm.c++/dropref.C (test for excess errors)
XFAIL: libitm.c++/dropref.C execution test
PASS: libitm.c++/eh-1.C (test for excess errors)
PASS: libitm.c++/eh-1.C execution test
UNSUPPORTED: libitm.c++/static_ctor.C
PASS: libitm.c++/throwdown.C (test for excess errors)
=== libitm Summary ===
# of expected passes 26
# of expected failures 3
# of unsupported tests 1
-Andi
--
ak@linux.intel.com -- Speaking for myself only