From: Ralf Baechle <ralf@oss.sgi.com>
To: Carsten Langgaard <carstenl@mips.com>
Cc: Jun Sun <jsun@mvista.com>, linux-mips@oss.sgi.com
Subject: Re: an old FPU context corruption problem when signal happens
Date: Wed, 2 Jan 2002 02:34:20 -0200 [thread overview]
Message-ID: <20020102023420.A8786@dea.linux-mips.net> (raw)
In-Reply-To: <3C2AFD8C.6BAA7F1@mips.com>; from carstenl@mips.com on Thu, Dec 27, 2001 at 11:53:00AM +0100
On Thu, Dec 27, 2001 at 11:53:00AM +0100, Carsten Langgaard wrote:
> You are welcome to find a better way of handling a non-fpu instruction in the
> delay slot of the fpu-branch instruction.
> But until someone find a better solution (that works, in all situation), I
> think we need this patch.
I could live with your solution if we'd be living in uniprocessor-land
only. Well, that time is over now ...
Ralf
prev parent reply other threads:[~2002-01-02 5:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-20 1:04 an old FPU context corruption problem when signal happens Jun Sun
2001-12-20 7:58 ` Carsten Langgaard
2001-12-20 17:16 ` Jun Sun
2001-12-25 6:41 ` Ralf Baechle
2001-12-25 6:51 ` Ralf Baechle
2001-12-27 10:53 ` Carsten Langgaard
2002-01-02 4:34 ` Ralf Baechle [this message]
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=20020102023420.A8786@dea.linux-mips.net \
--to=ralf@oss.sgi.com \
--cc=carstenl@mips.com \
--cc=jsun@mvista.com \
--cc=linux-mips@oss.sgi.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