From: Ralf Baechle <ralf@oss.sgi.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>, linux-mips@oss.sgi.com
Subject: Re: sti() does not work.
Date: Fri, 13 Jul 2001 13:35:18 +0200 [thread overview]
Message-ID: <20010713133517.C1378@bacchus.dhis.org> (raw)
In-Reply-To: <Pine.GSO.3.96.1010705132623.11517D-100000@delta.ds2.pg.gda.pl>; from macro@ds2.pg.gda.pl on Thu, Jul 05, 2001 at 01:35:11PM +0200
On Thu, Jul 05, 2001 at 01:35:11PM +0200, Maciej W. Rozycki wrote:
> > > (why is noreorder used here?).
> >
> > Without the .set noreorder the assembler would be free to do arbitrary
> > reordering of the object code generated. Gas doesn't do that but there
> > are other assemblers that do flow analysis and may generate object code
> > that doesn't look very much like the source they were fed with.
>
> Hmm, I would consider that a bug in such an assembler. The mtc0 and
> possibly the mfc0 opcode should be treated as reordering barriers as they
> may involve side effects an assembler might not be aware of.
Assembler is the art of using sideeffects so things are fairly explicit.
Optimizations are controlled using
.set noreorder / reorder
.set volatile / novolatile
.set nomove / nomove
.set nobopt / bopt
Ralf
next prev parent reply other threads:[~2001-07-13 13:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-03 22:48 sti() does not work Steven Liu
2001-07-03 22:48 ` Steven Liu
2001-07-04 10:23 ` Thiemo Seufer
2001-07-04 12:23 ` Gleb O. Raiko
2001-07-04 13:26 ` Ralf Baechle
2001-07-05 11:35 ` Maciej W. Rozycki
2001-07-13 11:35 ` Ralf Baechle [this message]
2001-07-13 14:01 ` Maciej W. Rozycki
2001-07-14 11:04 ` Ralf Baechle
2001-07-14 11:39 ` Kevin D. Kissell
2001-07-14 11:39 ` Kevin D. Kissell
2001-07-16 12:46 ` Maciej W. Rozycki
2001-07-04 13:29 ` Ralf Baechle
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=20010713133517.C1378@bacchus.dhis.org \
--to=ralf@oss.sgi.com \
--cc=ica2_ts@csv.ica.uni-stuttgart.de \
--cc=linux-mips@oss.sgi.com \
--cc=macro@ds2.pg.gda.pl \
/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