------- Comment #1 from rguenth at gcc dot gnu dot org 2007-11-24 17:58 -------
This is obviously not very useful information. You have to track this down
further. The usual process is
1) Build individual source files without optimization until you figure out
which file triggers the failure.
2) Play with GCC options, does -O1 work? Does -O2
{-fno-tree-vrp,-fno-tree-pre}
work? etc.
3) Narrow down the routine that makes the difference
4) Figure out if it's really a GCC problem.
--
rguenth at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34216
