[Bug target/11716] [mips] branch out of range when building fold-const.c
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11716
------- Additional Comments From rsandifo at redhat dot com 2003-08-09 09:23 -------
Subject: Re: [mips] branch out of range when building fold-const.c
"doko at cs dot tu-berlin dot de" <gcc-bugzilla@gcc.gnu.org> writes:
> rsandifo at redhat dot com writes:
> > Mainline gcc is supposed to get it right though. Could you attach
> > the preprocessed fold-const.i file?
>
> hmm, it's already attached. or is this the wrong one?
Ah, sorry about that. For some reason I'd assumed you were using 3.3 to
cross-compile 3.3 and trunk to cross-compile trunk. But it now occurs
to me that mips64-linux-gnu is new to 3.4, so I guess you were using 3.3
and trunk to compile the same version of gcc. Is that right?
When you say you're building a cross compiler, is it a cross-host
or a normal cross-target? It looks from bugzilla entry like it's
a cross-target, i.e.:
build: mips-linux-gnu
host: mips-linux-gnu
target: mips64-linux-gnu
In other words, the compiler itself is to run on mips-linux-gnu
rather than mips64-linux-gnu. Is that right?
I tried building an i686-pc-linux-gnu cross mips-linux-gnu compiler
from HEAD but couldn't reproduce the problem. The checkout I used
was updated yesterday.
Is it still a problem for you on HEAD? If so, could you tell me what
configure line you used? Also, could you try both -mexplicit-relocs
and -mno-explicit-relocs?
Richard
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
Reply to: