From: cgd@broadcom.com
To: macro@ds2.pg.gda.pl
Cc: "David Daney" <ddaney@avtrex.com>,
"Ralf Baechle" <ralf@linux-mips.org>,
linux-mips@linux-mips.org, binutils@sources.redhat.com
Subject: Re: [Patch] / 0 should send SIGFPE not SIGTRAP...
Date: Fri, 11 Jun 2004 19:28:00 -0000 [thread overview]
Message-ID: <yov57juduc7q.fsf@ldt-sj3-010.sj.broadcom.com> (raw)
In-Reply-To: <mailpost.1086981251.16853@news-sj1-1>
At Fri, 11 Jun 2004 19:14:11 +0000 (UTC), "Maciej W. Rozycki" wrote:
> 2. Gas should definitely use the codes consistently. And it's a pity the
> ABI got broken -- I think another mnemonic should have been chosen for the
> correct implementation of "break", available to any ISA.
in retrospect, the 'B' variation probably wasn't the greatest idea.
If it were removed (leaving 'c' and 'c','q' variations), I don't know
that any real harm would occur.
It may be very confusing to people who expect that the break code will
translate into the instruction in an obvious way, and obviously it
would mess up use of 20-bit codes, but i don't know how prevalent that
is.
Unfortunately, at this point, Linux should probably accept the
divide-by-zero code in both locations.
(Really, from day one, assemblers probably should have accepted a
20-bit code. I just checked my copy of the Kane r2000/r3000 book, and
it was 20-bit all the way back then. If i had to guess, i'd guess
that gas was copying a non-gnu assembler's behaviour. In any case,
water under the bridge.)
cgd
next prev parent reply other threads:[~2004-06-11 19:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <40C9F5A4.2050606@avtrex.com>
[not found] ` <40C9F5FE.8030607@avtrex.com>
2004-06-11 18:22 ` David Daney
2004-06-11 19:12 ` Maciej W. Rozycki
[not found] ` <mailpost.1086981251.16853@news-sj1-1>
2004-06-11 19:28 ` cgd [this message]
2004-06-11 19:50 ` Maciej W. Rozycki
2004-06-11 20:52 ` David Daney
2004-06-11 21:12 ` [Patch] (revised patch) " David Daney
2004-06-13 8:33 ` Geert Uytterhoeven
2004-06-14 12:52 ` Maciej W. Rozycki
2004-06-22 21:30 ` [Patch] " Maciej W. Rozycki
2004-06-23 19:33 ` David Daney
2004-06-23 19:38 ` Maciej W. Rozycki
2004-06-24 10:39 ` Richard Sandiford
2004-06-24 18:34 ` Maciej W. Rozycki
[not found] ` <mailpost.1088102121.25381@news-sj1-1>
2004-06-24 18:47 ` cgd
2004-06-28 13:46 ` Maciej W. Rozycki
2004-06-28 15:19 cgd
2004-06-28 15:36 ` Maciej W. Rozycki
2004-07-19 14:22 ` Maciej W. Rozycki
[not found] ` <mailpost.1090246948.15046@news-sj1-1>
2004-07-19 15:19 ` cgd
2004-07-19 15:42 ` Maciej W. Rozycki
2004-07-19 23:29 ` Thiemo Seufer
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=yov57juduc7q.fsf@ldt-sj3-010.sj.broadcom.com \
--to=cgd@broadcom.com \
--cc=binutils@sources.redhat.com \
--cc=ddaney@avtrex.com \
--cc=linux-mips@linux-mips.org \
--cc=macro@ds2.pg.gda.pl \
--cc=ralf@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).