public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ehrhardt@mathematik.uni-ulm.de
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, marcusma@lsl.co.uk,
	nobody@gcc.gnu.org
Subject: Re: target/7493: [SPRAC] Possible instruction jump too large for assembler.
Date: Tue, 10 Dec 2002 08:53:00 -0000	[thread overview]
Message-ID: <20021210165301.26131.qmail@sources.redhat.com> (raw)

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


             reply	other threads:[~2002-12-10 16:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-10  8:53 ehrhardt [this message]
2002-12-10  9:37 Marcus MacWilliam
2002-12-10  9:46 Christian Ehrhardt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20021210165301.26131.qmail@sources.redhat.com \
    --to=ehrhardt@mathematik.uni-ulm.de \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=marcusma@lsl.co.uk \
    --cc=nobody@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).