From: Alexandre Oliva <aoliva@redhat.com>
To: "H. J. Lu" <hjl@lucon.org>
Cc: Richard Sandiford <rsandifo@redhat.com>,
linux-mips@linux-mips.org, gcc@gcc.gnu.org,
binutils@sources.redhat.com
Subject: Re: MIPS gas relaxation still doesn't work
Date: Mon, 14 Oct 2002 12:28:00 -0000 [thread overview]
Message-ID: <orzntg298z.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <20021014105055.B30830@lucon.org>
On Oct 14, 2002, "H. J. Lu" <hjl@lucon.org> wrote:
> On Mon, Oct 14, 2002 at 02:43:26PM -0300, Alexandre Oliva wrote:
>> On Oct 14, 2002, "H. J. Lu" <hjl@lucon.org> wrote:
>>
>> > The problem here is when gcc fills the delay slot with nop, it kills
>> > branch relaxation.
>>
>> It wouldn't if only the delay slot was enclosed in .set nomacro.
> What do you mean by that?
Instead of:
.set noreorder
.set nomacro
b foo
nop
.set macro
.set reorder
perhaps we could emit:
.set noreorder
b foo
.set nomacro
nop
.set macro
.set reorder
Since b foo wouldn't be affected by nomacro, branch relaxing could
fix it up (the relaxations are delay-slot-safe).
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist Professional serial bug killer
next prev parent reply other threads:[~2002-10-14 17:58 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
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 [this message]
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=orzntg298z.fsf@free.redhat.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=hjl@lucon.org \
--cc=linux-mips@linux-mips.org \
--cc=rsandifo@redhat.com \
/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).