From: "Kevin D. Kissell" <kevink@mips.com>
To: "Jun Sun" <jsun@mvista.com>
Cc: <linux-mips@linux-mips.org>
Subject: Re: FCSR Management
Date: Tue, 24 Sep 2002 21:29:25 +0200 [thread overview]
Message-ID: <002501c26400$b7fc0640$10eca8c0@grendel> (raw)
In-Reply-To: 20020924103703.P14312@mvista.com
From: "Jun Sun" <jsun@mvista.com>
> > Am I missing something, or is this a problem?
> >
>
> FPE exceptions, actually almost all exceptions, are cleared before their
> handlers are invoked. See kernel/entry.S and look for BUILD_HANDLER().
>
> Those macro defines are really mind-twisting and usually don't show up on
> grep radar...
Right you are. Thanks. Maciej gave me a bit of a scare there. ;-)
In an ideal universe, the unmodified FCSR which is correctly
passed as a parameter to handle_fpe() (now that I look at entry.S,
it all comes back.. ;-) would be passed on as part of the
signal "payload" if SIGFPE is caught, but at least things
aren't drastically broken.
Kevin K.
WARNING: multiple messages have this Message-ID (diff)
From: "Kevin D. Kissell" <kevink@mips.com>
To: Jun Sun <jsun@mvista.com>
Cc: linux-mips@linux-mips.org
Subject: Re: FCSR Management
Date: Tue, 24 Sep 2002 21:29:25 +0200 [thread overview]
Message-ID: <002501c26400$b7fc0640$10eca8c0@grendel> (raw)
Message-ID: <20020924192925.bjIFdmKfKdtSSyAvWbL69a5kV6eA1Z0lSL-9B556mFo@z> (raw)
In-Reply-To: 20020924103703.P14312@mvista.com
From: "Jun Sun" <jsun@mvista.com>
> > Am I missing something, or is this a problem?
> >
>
> FPE exceptions, actually almost all exceptions, are cleared before their
> handlers are invoked. See kernel/entry.S and look for BUILD_HANDLER().
>
> Those macro defines are really mind-twisting and usually don't show up on
> grep radar...
Right you are. Thanks. Maciej gave me a bit of a scare there. ;-)
In an ideal universe, the unmodified FCSR which is correctly
passed as a parameter to handle_fpe() (now that I look at entry.S,
it all comes back.. ;-) would be passed on as part of the
signal "payload" if SIGFPE is caught, but at least things
aren't drastically broken.
Kevin K.
next prev parent reply other threads:[~2002-09-24 19:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-24 7:51 FCSR Management Kevin D. Kissell
2002-09-24 7:51 ` Kevin D. Kissell
2002-09-24 11:42 ` Maciej W. Rozycki
2002-09-24 12:37 ` Kevin D. Kissell
2002-09-24 12:37 ` Kevin D. Kissell
2002-09-24 17:37 ` Jun Sun
2002-09-24 19:29 ` Kevin D. Kissell [this message]
2002-09-24 19:29 ` Kevin D. Kissell
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='002501c26400$b7fc0640$10eca8c0@grendel' \
--to=kevink@mips.com \
--cc=jsun@mvista.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