public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "H. J. Lu" <hjl@lucon.org>
To: aoliva@redhat.com, linux-mips@linux-mips.org, gcc@gcc.gnu.org
Cc: binutils@sources.redhat.com
Subject: Re: MIPS gas relaxation still doesn't work
Date: Mon, 14 Oct 2002 09:23:00 -0000	[thread overview]
Message-ID: <20021014082810.A28682@lucon.org> (raw)
In-Reply-To: <20021013145423.A10174@lucon.org>; from hjl@lucon.org on Sun, Oct 13, 2002 at 02:54:23PM -0700

On Sun, Oct 13, 2002 at 02:54:23PM -0700, H. J. Lu wrote:
> On Sat, Oct 12, 2002 at 11:34:23AM -0700, H. J. Lu wrote:
> > Hi Alexandre,
> > 
> > I don't think your MIPS gas relaxation works. I got
> > 
> > # mipsel-linux-gcc /export/gnu/src/gcc-3.2/gcc/gcc/testsuite/g++.dg/opt/longbranch1.C
> > /tmp/cc0rrnMz.s: Assembler messages:
> > /tmp/cc0rrnMz.s:33733: Error: Branch out of range
> > /tmp/cc0rrnMz.s:33740: Error: Branch out of range
> > 
> > Could you please verify it?
> > 
> 
> Here is a small testcase extracted from gcc. I got
> 
> # mipsel-linux-gcc -c foo.s 
> foo.s: Assembler messages:
> foo.s:7: Error: Branch out of range
> 
> You may say it is a gcc bug. But I don't remember to see SGI assmebler
> have any problem with g++.dg/opt/longbranch1.C. Does gcc generate
> different code for Irix from Linux? Is it really unsafe to do branch
> relaxation when macro is off.
> 
> 

Here is a testcase which gas refuses to relax. I have 2 questions:

1. Does the SGI mips assembler relax it?
2. Is noreorder/nomacro really needed for gas? If I remeber right, it
is safe for gas to use

foo:
	j foo

Can gcc be be modified not to generate noreorder/nomacro for branchs if
gas is used?


H.J.
--foo.s---
foo:
	.space	0x20000
	.set    noreorder
	.set    nomacro
	j	foo
	nop
	.set    macro
	.set    reorder

       reply	other threads:[~2002-10-14 15:28 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20021012113423.A27894@lucon.org>
     [not found] ` <20021013145423.A10174@lucon.org>
2002-10-14  9:23   ` H. J. Lu [this message]
2002-10-14  9:35     ` Richard Sandiford
2002-10-14  9:37       ` H. J. Lu
2002-10-14 10:04         ` Richard Sandiford
2002-10-14 10:43           ` H. J. Lu
2002-10-14 10:50             ` David S. Miller
2002-10-14 10:53               ` H. J. Lu
2002-10-14 11:13             ` Alexandre Oliva
2002-10-14 11:21               ` H. J. Lu
2002-10-14 12:28                 ` Alexandre Oliva
2002-10-14 12:37                   ` H. J. Lu
2002-10-14 12:58                     ` Alexandre Oliva
2002-10-14 13:00                       ` H. J. Lu
2002-10-14 13:08                         ` David S. Miller
2002-10-14 13:23                           ` H. J. Lu
2002-10-14 14:04                             ` David S. Miller
2002-10-14 14:14                               ` H. J. Lu
2002-10-14 14:17                                 ` Alexandre Oliva
2002-10-14 14:18                                   ` H. J. Lu
2002-10-14 15:37                                     ` Alexandre Oliva
2002-10-14 15:40                                       ` H. J. Lu
2002-10-15  1:08                                         ` Alexandre Oliva
2002-10-15  2:53                                           ` Dominic Sweetman
2002-10-15  8:12                                             ` Alexandre Oliva
2002-10-15 14:18                                             ` Jim Wilson
2002-10-15 13:27                                           ` Maciej W. Rozycki
2002-10-15 16:37                                             ` Jim Wilson
2002-10-16  6:39                                               ` Maciej W. Rozycki
2002-10-16 10:38                                                 ` Jim Wilson
2002-10-15 18:40                                             ` Alexandre Oliva
2002-10-16  7:01                                               ` Maciej W. Rozycki
2002-10-16  7:47                                                 ` Alexandre Oliva
2002-10-16  8:06                                                   ` Maciej W. Rozycki
2002-10-14 17:02                                     ` Eric Christopher
2002-10-15  1:15                                       ` Alexandre Oliva
2002-10-14 14:44                                   ` Michael Matz
2002-10-15 13:28                         ` Jim Wilson
2002-10-15 13:45                           ` Paul Koning
2002-10-15 14:32                             ` Maciej W. Rozycki
2002-10-15 15:33                               ` Alexandre Oliva
2002-10-16  5:32                                 ` Maciej W. Rozycki
2002-10-15 14:00                           ` Daniel Jacobowitz
2002-10-15 14:56                             ` Eric Christopher
2002-10-15 15:05                               ` Daniel Jacobowitz
2002-10-16  7:53                                 ` Paul Koning
2002-10-16  8:11                                   ` Maciej W. Rozycki
2002-10-15 15:23                             ` Jim Wilson
2002-10-16  5:38                               ` Maciej W. Rozycki
2002-10-16 10:37                                 ` Jim Wilson
2002-10-16 11:04                                   ` Maciej W. Rozycki
2002-10-15 16:54                         ` Richard Henderson
2002-10-14  9:40     ` Alexandre Oliva
2002-10-14  9:44       ` H. J. Lu

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=20021014082810.A28682@lucon.org \
    --to=hjl@lucon.org \
    --cc=aoliva@redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=linux-mips@linux-mips.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).