From: Paul Koning <pkoning@equallogic.com>
To: wilson@redhat.com
Cc: hjl@lucon.org, aoliva@redhat.com, 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: Tue, 15 Oct 2002 16:02:50 -0400 [thread overview]
Message-ID: <15788.29802.865689.741487@pkoning.dev.equallogic.com> (raw)
In-Reply-To: xwusmz7xym6.fsf@tonopah.toronto.redhat.com
>>>>> "Jim" == Jim Wilson <wilson@redhat.com> writes:
>> Can gcc not to emit nop nor noreorder when it tries to fill the
>> delay slot with nop?
Jim> You never want the assembler to try to fill delay slots.
Jim> Consider a compiler optimization like software pipelining. ...
Jim> Meanwhile, we need to get out of
Jim> the habit of relying on assembler optimizations. In the long
Jim> run, assembler optimizations are bad, and we need to stop using
Jim> them as soon as possible. Gcc should emit .set
Jim> nomacro/noreorder/noat/etc at the begining of its assembly
Jim> output, and never turn them on.
Makes sense to me. As an assembly language programmer, I do the same
thing in handwritten code, for the same reasons.
paul
next prev parent reply other threads:[~2002-10-15 20:03 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20021012113423.A27894@lucon.org>
[not found] ` <20021013145423.A10174@lucon.org>
[not found] ` <20021014082810.A28682@lucon.org>
2002-10-14 16:09 ` MIPS gas relaxation still doesn't work Richard Sandiford
[not found] ` <20021014091649.A29353@lucon.org>
2002-10-14 16:35 ` Richard Sandiford
[not found] ` <20021014101640.A30133@lucon.org>
2002-10-14 17:13 ` David S. Miller
2002-10-14 17:43 ` Alexandre Oliva
[not found] ` <20021014105055.B30830@lucon.org>
2002-10-14 17:58 ` Alexandre Oliva
[not found] ` <20021014110118.B30940@lucon.org>
2002-10-14 19:37 ` Alexandre Oliva
[not found] ` <20021014123940.A32333@lucon.org>
2002-10-14 19:35 ` David S. Miller
[not found] ` <20021014125549.A32575@lucon.org>
2002-10-14 19:51 ` David S. Miller
[not found] ` <20021014130932.A32693@lucon.org>
2002-10-14 20:20 ` Alexandre Oliva
2002-10-14 21:04 ` Michael Matz
2002-10-14 21:04 ` Michael Matz
[not found] ` <20021014132352.A489@lucon.org>
2002-10-14 21:06 ` Alexandre Oliva
[not found] ` <20021014141442.A1158@lucon.org>
2002-10-15 5:00 ` Alexandre Oliva
2002-10-15 8:15 ` Dominic Sweetman
2002-10-15 13:48 ` Alexandre Oliva
2002-10-15 20:19 ` Jim Wilson
2002-10-15 19:37 ` Maciej W. Rozycki
2002-10-15 22:32 ` Jim Wilson
2002-10-16 11:03 ` Maciej W. Rozycki
2002-10-16 16:43 ` Jim Wilson
2002-10-16 0:16 ` Alexandre Oliva
2002-10-16 11:06 ` Maciej W. Rozycki
2002-10-16 13:36 ` Alexandre Oliva
2002-10-16 14:13 ` Maciej W. Rozycki
2002-10-14 21:25 ` Eric Christopher
2002-10-15 5:01 ` Alexandre Oliva
2002-10-15 19:58 ` Jim Wilson
2002-10-15 20:02 ` Paul Koning [this message]
2002-10-15 20:28 ` Maciej W. Rozycki
2002-10-15 21:49 ` Alexandre Oliva
2002-10-16 10:25 ` Maciej W. Rozycki
2002-10-15 22:43 ` Richard Henderson
2002-10-14 16:19 ` Alexandre Oliva
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=15788.29802.865689.741487@pkoning.dev.equallogic.com \
--to=pkoning@equallogic.com \
--cc=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 \
--cc=wilson@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.