What do you suggest, a bug report per failure with nothing but the
directory/name of the test?
I'd say a bug report for each distinct failure. It can get awful
confusing when there's multiple bugs in a single PR...
Done. PR numbers below.
There is no trans-mem or libitm component, so I had to select other.
Thanks for your patience.
51163 nor P3 unassig...@gcc.gnu.org NEW --- gcc.dg/tm/alias-1.c
failure
51164 nor P3 unassig...@gcc.gnu.org NEW --- gcc.dg/tm/alias-2.c
failure
51165 nor P3 unassig...@gcc.gnu.org NEW --- gcc.dg/tm/memopt-3.c
failure
51166 nor P3 unassig...@gcc.gnu.org NEW --- gcc.dg/tm/memopt-4.c
failure
51167 nor P3 unassig...@gcc.gnu.org NEW --- gcc.dg/tm/memopt-5.c
failure
51168 nor P3 unassig...@gcc.gnu.org NEW --- gcc.dg/tm/memopt-7.c
failure
51169 nor P3 unassig...@gcc.gnu.org NEW --- XFAIL:
libitm.c/dropref-2.c execution test
51170 nor P3 unassig...@gcc.gnu.org NEW --- XFAIL:
libitm.c/dropref.c execution test
51171 nor P3 unassig...@gcc.gnu.org NEW --- XFAIL:
libitm.c/reentrant.c execution test
51172 nor P3 unassig...@gcc.gnu.org NEW --- XFAIL:
libitm.c++/dropref.C execution test
51173 nor P3 unassig...@gcc.gnu.org NEW --- XFAIL:
libitm.c++/static_ctor.C
