[18:22] < apinski> /home/apinski/src/local/gcc/gcc/testsuite/gcc.c-torture/execute/930921-1.c:5: error: could not split insn^M [18:22] < apinski> new failure [18:23] < apinski> on ppc-linux-gnu [18:23] < apinski> between 127935 and 128000
[18:32] < Rhyolite> I guess it could be due to my predicate change [18:33] < apinski> this was after that [18:33] < Rhyolite> okay, phew [18:33] < apinski> paired support was inbetween that though [18:33] < Rhyolite> sigh [18:34] < Rhyolite> Revital said that she regression tested [18:34] < apinski> but also Sandra's regclass changes [18:34] < apinski> and some optabs changes [18:34] < apinski> so it could be either of those three And then from PR 33277 #3: Fromp http://gcc.gnu.org/ml/gcc-testresults/, looking at the results from "regress", it can be narrowed between 127961 (working) and 127997 (non working). Note that the last change of final.c is 127941 (outside the range). >From an uneducated guess, I'l say 127989, but I may be completely wrong. And from #4: >From looking closer to the changes, the scheduler changes is not likely because this happens at -O1 :) I am more thinking it was: 2007-08-31 Richard Sandiford <[EMAIL PROTECTED]> Which changed optabs which is part of the expansion. The IV change could not have cause this issue as there is no loop in that function so the last change would be the optabs change. -- Summary: [4.3 Regression] gcc.c-torture/execute/930921-1.c fails at -O1 and above now Product: gcc Version: 4.3.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P3 Component: middle-end AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: pinskia at gcc dot gnu dot org GCC target triplet: powerpc-*-* (32bits) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33283
