From: Ralf Baechle <ralf@linux-mips.org>
To: Andrew Haley <aph@redhat.com>
Cc: David Daney <ddaney@avtrex.com>,
gcc@gcc.gnu.org, linux-mips@linux-mips.org, java@gcc.gnu.org
Subject: Re: [RFC] MIPS division by zero and libgcj...
Date: Thu, 10 Jun 2004 22:27:51 +0200 [thread overview]
Message-ID: <20040610202751.GA5816@linux-mips.org> (raw)
In-Reply-To: <16584.46883.332620.513805@cuddles.cambridge.redhat.com>
On Thu, Jun 10, 2004 at 08:31:47PM +0100, Andrew Haley wrote:
> I thought that the MIPS never generated a hardware trap for division,
> but instead there was an assembler macro that did the test for
> overflow, and the "div" instruction actually generates this test
> inline. Maybe do a disassembly to check.
Linux/MIPS's behaviour is consistent with all MIPS UNIX flavours I know
of both those following the SysV ABI and others such as Ultrix.
Ralf
next prev parent reply other threads:[~2004-06-10 20:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-10 19:12 [RFC] MIPS division by zero and libgcj David Daney
2004-06-10 19:31 ` Andrew Haley
2004-06-10 19:39 ` Andrew Haley
2004-06-10 19:48 ` David Daney
2004-06-10 19:58 ` Andrew Haley
2004-06-10 20:31 ` David Daney
2004-06-10 20:27 ` Ralf Baechle [this message]
2004-06-11 14:01 ` Maciej W. Rozycki
2004-06-11 15:34 ` David Daney
2004-06-11 15:39 ` 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=20040610202751.GA5816@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=aph@redhat.com \
--cc=ddaney@avtrex.com \
--cc=gcc@gcc.gnu.org \
--cc=java@gcc.gnu.org \
--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