public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Eric Ries" <eries@there.com>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: FPU precision & signal handlers (bug?)
Date: Mon, 4 Mar 2002 15:31:26 -0800	[thread overview]
Message-ID: <KPEDLFEJBNHDLFEEOIIMCELKCEAA.eries@there.com> (raw)
In-Reply-To: <E16i15h-0000q9-00@the-village.bc.nu>

> -----Original Message-----
> From: Alan Cox [mailto:alan@lxorguk.ukuu.org.uk]
> Sent: Monday, March 04, 2002 2:38 PM
> To: Eric Ries
> Cc: linux-kernel@vger.kernel.org
> Subject: Re: FPU precision & signal handlers (bug?)
>
>
> Think about MMX and hopefully it makes sense then.

Yes, I think I understand why this is the case presently.

> > strikes me as kind of a hack. Why should the signal handler, alone
> > among all my functions (excepting main) be responsible for blowing
> > away the control word?
>
> Right - I would expect it to be restored at the end of the signal handler
> for you - is that occuring or not ? I just want to make sure I understand
> the precise details of the problem here.

Yes, my belief is that the kernel undoes the FINIT changes by restoring the
FPU state after the signal handler returns.

Eric


  reply	other threads:[~2002-03-04 23:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-04 18:58 FPU precision & signal handlers (bug?) Eric Ries
2002-03-04 22:37 ` Alan Cox
2002-03-04 23:31   ` Eric Ries [this message]
2002-03-05 18:23   ` Gabriel Paubert
2002-03-06  0:06     ` Alan Cox
2002-03-07 17:31       ` Gabriel Paubert
2002-03-07 19:25         ` Alan Cox
2002-03-08 12:11           ` Gabriel Paubert
2002-03-06 19:11 ` Gabriel Paubert
2002-03-06 23:32   ` Eric Ries
2002-03-08 11:54     ` Gabriel Paubert

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=KPEDLFEJBNHDLFEEOIIMCELKCEAA.eries@there.com \
    --to=eries@there.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.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