This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/11699] internal compiler error, unrecognized instruction.
- From: "cgd at broadcom dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 29 Jul 2003 17:49:30 -0000
- Subject: [Bug target/11699] internal compiler error, unrecognized instruction.
- References: <20030728220936.11699.cgd@broadcom.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11699
------- Additional Comments From cgd at broadcom dot com 2003-07-29 17:49 -------
Subject: Re: internal compiler error, unrecognized
instruction.
At 29 Jul 2003 17:43:46 -0000, pinskia at physics dot uc dot edu wrote:
> Since the option -mexplicit-relocs did not exist before 3.4, this is not a regression.
Let me try to spin this my way. 8-)
Consider the args:
-G0 -mabicalls pr11699.c
gcc 3.3 + stock binutils of approximately same vintage:
works fine as far as i know. I've not tested it, but I've
never seen problems like this before...
CVS gcc + CVS binutils of same vintage:
crashes.
no "-mexplicit-relocs" options is needed in the latter case, because
-mexplicit-relocs is the *default*.
I.e., compiling this test program with "-G0 -mabicalls" on top of the
built-in defaults used to work, and now does not.
So, regression.
On simple solution to the regression would be to disable
-mexplicit-relocs by default, but that would seriously bite. 8-)
(I can provide you the scripts that i use to checkout and combine, if
that'd help you demonstrate to your satisfaction.)
chris