[Bug middle-end/33277] [4.3 Regression] Bootstrap check failures ICE's

["dominiq at lps dot ens dot fr" <gcc-bugzilla@gcc.gnu.org>]

------- Comment #3 from dominiq at lps dot ens dot fr  2007-09-02 13:42 -------
> [18:23] < apinski> between 127935 and 128000

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.

>You know, there are many different targets that GCC supports, sometimes the
> patch does not cause any regression on one target can cause regressions on
> others.  This happens all the time.  You need to understand the main reason why
> we have the testsuite is so we easily see when a target has a regression or
> not.

Yes indeed! but the maintainers could look at the above URL to check that there
is no unexpected regression on untested platforms. If they have no access to
some of them, there could be a list of people to ask for details about the
failure (I volunteer for Darwin!).

Otherwise I fully agree with Andrew Pinski about what should not put in bug
reports.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33277