------- Comment #40 from iains at gcc dot gnu dot org 2010-06-04 18:45 ------- (In reply to comment #39) > I confirm that the failures for libjava reported in comment #33 were due to > some misconfiguration. > With the patches in http://gcc.gnu.org/bugzilla/attachment.cgi?id=20762 and > http://gcc.gnu.org/bugzilla/attachment.cgi?id=20822 , after a clean boostrap, > I > see the following new failures: > > FAIL: g++.dg/tls/init-2.C (internal compiler error) > FAIL: g++.dg/tls/init-2.C (test for excess errors) > > FAIL: gcc.dg/tls/asm-1.c (internal compiler error) > FAIL: gcc.dg/tls/asm-1.c (test for errors, line 7) > FAIL: gcc.dg/tls/asm-1.c (test for excess errors) > > FAIL: obj-c++.dg/tls/init-2.mm -fgnu-runtime (internal compiler error) > FAIL: obj-c++.dg/tls/init-2.mm -fnext-runtime (internal compiler error)
right, that's what I expect. I think this : gcc.dg/tls/asm-1.c is because gimplify_asm () doesn't consider expansion of the parameter (hopefully Honza could help with that). I think that this : g++.dg/tls/init-2.C & obj-c++.dg/tls/init-2.mm - (which are the same code) are down to two conflicting error responses from the C++ FE, -- there are two error messages that disagree. In other words, although these are regressions showing from the application of the patch - I think they might be latent problems outside emutls. I'll re-jig the patch to remove the ABI breakage and post over the next few days. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44132
