This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: target/7493: [SPRAC] Possible instruction jump too large for assembler.
- From: ehrhardt at mathematik dot uni-ulm dot de
- To: gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, marcusma at lsl dot co dot uk, nobody at gcc dot gnu dot org
- Date: 10 Dec 2002 16:53:01 -0000
- Subject: Re: target/7493: [SPRAC] Possible instruction jump too large for assembler.
- Reply-to: ehrhardt at mathematik dot uni-ulm dot de, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, marcusma at lsl dot co dot uk, nobody at gcc dot gnu dot org, gcc-gnats at gcc dot gnu dot org
Old Synopsis: Possible instruction jump too large for assembler.
New Synopsis: [SPRAC] Possible instruction jump too large for assembler.
State-Changed-From-To: open->feedback
State-Changed-By: cae
State-Changed-When: Tue Dec 10 08:52:59 2002
State-Changed-Why:
The problem in the assembler output is an instructions sequence
like this on sparc:
call f,0
add %o7,(.LL100-.-4),%o7
which is compiled by GNU as without a warning even if the result
of .LL100-.-4 is larger than 4095, SUN as complains about the error though.
However, I can't get gcc to produce such assemble code. I did a few tests
with 3.3. and 2.95.3 but gcc always detected that the jump distance is
more than what can be added to o7 with a single add instruction and
replaced the add with a ``nop; b,a .LL100'' sequence.
To debug this further we'll need a self contained testcase, i.e.
preprocessed source (see -save-temps option, the .i file is what we're
interested in). Due to the nature of the bug a single function (with
everything it needs to compile!) will probably suffice as a useful testcase.
regards Christian Ehrhardt
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7493