From: David Daney <ddaney@avtrex.com>
To: David Daney <ddaney@avtrex.com>
Cc: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>,
cgd@broadcom.com, Ralf Baechle <ralf@linux-mips.org>,
linux-mips@linux-mips.org, binutils@sources.redhat.com
Subject: Re: [Patch] (revised patch) / 0 should send SIGFPE not SIGTRAP
Date: Fri, 11 Jun 2004 14:10:59 -0700 [thread overview]
Message-ID: <40CA1FE3.9030507@avtrex.com> (raw)
In-Reply-To: <40CA1B35.6010603@avtrex.com>
[-- Attachment #1: Type: text/plain, Size: 260 bytes --]
David Daney wrote:
> How about the attached (lightly tested) patch?
>
I will quit sending patches after this one. It is equivalent to the
previous version, except it uses the symbolic names of the break codes
instead of the numeric values.
David Daney.
[-- Attachment #2: traps.diff --]
[-- Type: text/plain, Size: 2382 bytes --]
*** ../linux-avtrex/linux/arch/mips/kernel/traps.c 2004-02-26 11:14:09.000000000 -0800
--- arch/mips/kernel/traps.c 2004-06-11 14:04:52.000000000 -0700
***************
*** 38,43 ****
--- 38,44 ----
#include <asm/traps.h>
#include <asm/uaccess.h>
#include <asm/mmu_context.h>
+ #include <asm/break.h>
extern asmlinkage void handle_mod(void);
extern asmlinkage void handle_tlbl(void);
***************
*** 597,615 ****
* There is the ancient bug in the MIPS assemblers that the break
* code starts left to bit 16 instead to bit 6 in the opcode.
* Gas is bug-compatible ...
! */
! bcode = ((opcode >> 16) & ((1 << 20) - 1));
!
! /*
* (A short test says that IRIX 5.3 sends SIGTRAP for all break
* insns, even for break codes that indicate arithmetic failures.
* Weird ...)
* But should we continue the brokenness??? --macro
*/
switch (bcode) {
! case 6:
! case 7:
! if (bcode == 7)
info.si_code = FPE_INTDIV;
else
info.si_code = FPE_INTOVF;
--- 598,622 ----
* There is the ancient bug in the MIPS assemblers that the break
* code starts left to bit 16 instead to bit 6 in the opcode.
* Gas is bug-compatible ...
! *
* (A short test says that IRIX 5.3 sends SIGTRAP for all break
* insns, even for break codes that indicate arithmetic failures.
* Weird ...)
* But should we continue the brokenness??? --macro
+ *
+ * It seems some assemblers (binutils-2.15 for example) assemble
+ * break correctly. So we check for the break code in either
+ * position.
+ *
*/
+
+ bcode = ((opcode >> 6) & ((1 << 20) - 1));
switch (bcode) {
! case BRK_OVERFLOW:
! case BRK_DIVZERO:
! case BRK_OVERFLOW << 10:
! case BRK_DIVZERO << 10:
! if (bcode == BRK_DIVZERO || bcode == (BRK_DIVZERO << 10))
info.si_code = FPE_INTDIV;
else
info.si_code = FPE_INTOVF;
***************
*** 633,639 ****
/* Immediate versions don't provide a code. */
if (!(opcode & OPCODE))
! tcode = ((opcode >> 6) & ((1 << 20) - 1));
/*
* (A short test says that IRIX 5.3 sends SIGTRAP for all trap
--- 640,646 ----
/* Immediate versions don't provide a code. */
if (!(opcode & OPCODE))
! tcode = ((opcode >> 6) & ((1 << 10) - 1));
/*
* (A short test says that IRIX 5.3 sends SIGTRAP for all trap
next prev parent reply other threads:[~2004-06-11 21:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-11 18:10 [Patch] / 0 should send SIGFPE not SIGTRAP David Daney
2004-06-11 18:12 ` David Daney
2004-06-11 18:20 ` David Daney
2004-06-11 19:12 ` Maciej W. Rozycki
[not found] ` <mailpost.1086981251.16853@news-sj1-1>
2004-06-11 19:27 ` cgd
2004-06-11 19:50 ` Maciej W. Rozycki
2004-06-11 20:51 ` David Daney
2004-06-11 21:10 ` David Daney [this message]
2004-06-13 8:33 ` [Patch] (revised patch) " Geert Uytterhoeven
2004-06-14 12:52 ` Maciej W. Rozycki
2004-06-22 21:30 ` [Patch] " Maciej W. Rozycki
2004-06-23 19:30 ` 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:46 ` 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=40CA1FE3.9030507@avtrex.com \
--to=ddaney@avtrex.com \
--cc=binutils@sources.redhat.com \
--cc=cgd@broadcom.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