From: Greg Lindahl <lindahl@keyresearch.com>
To: linux mips mailing list <linux-mips@linux-mips.org>
Subject: Re: [PATCH]: fix compiler warnings in the math-emulator
Date: Wed, 18 Dec 2002 13:27:26 -0800 [thread overview]
Message-ID: <20021218132726.A2572@wumpus.internal.keyresearch.com> (raw)
In-Reply-To: <Pine.GSO.3.96.1021218220828.14826A-100000@delta.ds2.pg.gda.pl>; from macro@ds2.pg.gda.pl on Wed, Dec 18, 2002 at 10:09:37PM +0100
> > Sometimes you don't care whether you do only "half" a macro instruction
> > if the branch is taken. Usually though, the warning is a good thing - I
> > remember having spent many hours finding bugs like this with assemblers
> > that don't issue warnings.
>
> This is exactly what ".set nomacro" is for -- I can't see any reason for
> such warnings when ".set macro" is active.
While in general I like playing with sharp knives (you should see my
cluster admin toolkit), and I like my kernel to run fast, and the only
thing that gets trashed is usually at, I still think I'd prefer to
have nops in those delay slots in the kernel. Hand-written assembly is
unlikely to use ".set nomacro" properly.
-- greg
next prev parent reply other threads:[~2002-12-18 21:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-18 1:43 [PATCH]: fix compiler warnings in the math-emulator Juan Quintela
2002-12-18 16:43 ` Maciej W. Rozycki
2002-12-18 17:51 ` Juan Quintela
2002-12-18 18:47 ` Maciej W. Rozycki
2002-12-18 19:42 ` Greg Lindahl
2002-12-18 19:50 ` Hartvig Ekner
2002-12-18 19:50 ` Hartvig Ekner
2002-12-18 21:09 ` Maciej W. Rozycki
2002-12-18 21:27 ` Greg Lindahl [this message]
2002-12-18 22:27 ` Juan Quintela
2002-12-19 11:52 ` Maciej W. Rozycki
2002-12-18 22:21 ` Juan Quintela
2002-12-19 11:44 ` Maciej W. Rozycki
2002-12-19 0:20 ` Ralf Baechle
2002-12-19 11:09 ` Maciej W. Rozycki
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=20021218132726.A2572@wumpus.internal.keyresearch.com \
--to=lindahl@keyresearch.com \
--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