This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug target/35839] [4.4 Regression] Altivec with the vectorizer causes an ICE in rs6000_check_sdmode



------- Comment #4 from dominiq at lps dot ens dot fr  2008-04-08 15:06 -------
My understanding of "gcc_assert" is that it is meant to trigger ICEs for
forbidden paths. Hence introducing new "gcc_assert" is likely to trigger ICEs,
including during bootstrap, either because of a rampant bug or because the
condition is too broad, as it seems to be the case here. So I think maintainers
should be very careful when they add new "gcc_assert" and monitor the
gcc-testresults mailing list for missing regular testers.

In particular, such modification on powerpc should be correlated to "regress":

regress

2008-04-01 07:19 Results for 4.4.0 20080331 (experimental) (GCC) testsuite on
powerpc-apple-darwin8.5.0
2008-04-01 16:27 Results for 4.4.0 20080401 (experimental) (GCC) testsuite on
powerpc-apple-darwin8.5.0
2008-04-03 13:29 Results for 4.4.0 20080403 (experimental) (GCC) testsuite on
powerpc-apple-darwin8.5.0
2008-04-03 21:27 Results for 4.4.0 20080403 (experimental) (GCC) testsuite on
powerpc-apple-darwin8.5.0
2008-04-04 05:26 Results for 4.4.0 20080403 (experimental) (GCC) testsuite on
powerpc-apple-darwin8.5.0
2008-04-04 13:25 Results for 4.4.0 20080404 (experimental) (GCC) testsuite on
powerpc-apple-darwin8.5.0
2008-04-04 21:23 Results for 4.4.0 20080404 (experimental) (GCC) testsuite on
powerpc-apple-darwin8.5.0

which gives a new result every ~8 hours and has stopped to do so since April
4th (this is why I did a fresh bootstrap in order to know what was going
wrong).


-- 


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]