[Bug c/30259] [4.1 branch] ICE on valid code
joseph at codesourcery dot com
gcc-bugzilla@gcc.gnu.org
Tue Dec 19 21:34:00 GMT 2006
------- Comment #3 from joseph at codesourcery dot com 2006-12-19 21:34 -------
Subject: Re: [4.1 branch] ICE on valid code
On Tue, 19 Dec 2006, edmar at freescale dot com wrote:
> Still, On December 16 I had a complete build, and on December 17 I have an ICE.
> It feels more like a regression than moving forward...
A complete build with, no doubt, all C++ tests failing with the problem
you noted in <http://gcc.gnu.org/ml/gcc/2006-09/msg00126.html>. Because
such a build is not particularly useful, I have taken a base with
t-ppccomm hacked to avoid building libgcc with -mlong-double-128 as the
appropriate baseline for testing.
It might be possible to do such a hack more cleanly by changing
ifneq (,$findstring gnu,$(target))
...
endif
to
ifneq (,$findstring gnu,$(target))
ifeq (,$findstring gnuspe,$(target))
...
endif
endif
and this might be appropriate for 4.1 branch to allow a default build to
complete cleanly. There may also be a particular bit of my long double
patch <http://gcc.gnu.org/ml/gcc-patches/2006-12/msg01388.html> that would
allow libgcc to build (but still be broken) without modifying t-ppccomm;
in particular, I'd suggest trying the change to
rs6000_legitimate_offset_address_p.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30259
More information about the Gcc-bugs
mailing list