From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: cgd@broadcom.com
Cc: binutils@sources.redhat.com, ddaney@avtrex.com,
linux-mips@linux-mips.org, ralf@linux-mips.org,
rsandifo@redhat.com
Subject: Re: [Patch] / 0 should send SIGFPE not SIGTRAP...
Date: Mon, 28 Jun 2004 15:36:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.55.0406281734560.23162@jurand.ds.pg.gda.pl> (raw)
In-Reply-To: <200406281519.IAA29663@mail-sj1-2.sj.broadcom.com>
On Mon, 28 Jun 2004 cgd@broadcom.com wrote:
> personally, i'd make the comment on the 'break' testcase in mips32.s a bit
> clearer and more explicit. e.g. "for a while, break for mips32
> took a 20 bit code. But that was incompatible and caused problems, so
> now it's back to the old 10 bit code, or two comma-separated 10 bit codes."
No problem.
> Otherwise, people might look and say "huh?"
;-)
next prev parent reply other threads:[~2004-06-28 15:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-28 15:19 cgd
2004-06-28 15:36 ` Maciej W. Rozycki [this message]
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
[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
2004-06-11 19:50 ` Maciej W. Rozycki
2004-06-11 20:52 ` David Daney
2004-06-22 21:30 ` 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
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=Pine.LNX.4.55.0406281734560.23162@jurand.ds.pg.gda.pl \
--to=macro@linux-mips.org \
--cc=binutils@sources.redhat.com \
--cc=cgd@broadcom.com \
--cc=ddaney@avtrex.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@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).