From: Carsten Langgaard <carstenl@mips.com>
To: Ralf Baechle <ralf@oss.sgi.com>
Cc: Jun Sun <jsun@mvista.com>, linux-mips@oss.sgi.com
Subject: Re: an old FPU context corruption problem when signal happens
Date: Thu, 27 Dec 2001 11:53:00 +0100 [thread overview]
Message-ID: <3C2AFD8C.6BAA7F1@mips.com> (raw)
In-Reply-To: 20011225044125.A16759@dea.linux-mips.net
Ralf Baechle wrote:
> On Thu, Dec 20, 2001 at 08:58:51AM +0100, Carsten Langgaard wrote:
>
> > Are you sure this hasn't been fix in the latest sources (2.4.16) ?
> > I have send a patch to Ralf, which I believe solves a similar problem as
> > you describe below.
> >
> > Ralf have you applied the patch ?
>
> Well, I applied it but it's really broken as something can be. Just an
> example:
>
> + /*
> + * FPU emulator may have it's own trampoline active just
> + * above the user stack, 16-bytes before the next lowest
> + * 16 byte boundary. Try to avoid trashing it.
> + */
> + sp -= 32;
>
> So the whole thing needs some overhaul.
>
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.
> Ralf
--
_ _ ____ ___ Carsten Langgaard Mailto:carstenl@mips.com
|\ /|||___)(___ MIPS Denmark Direct: +45 4486 5527
| \/ ||| ____) Lautrupvang 4B Switch: +45 4486 5555
TECHNOLOGIES 2750 Ballerup Fax...: +45 4486 5556
Denmark http://www.mips.com
next prev parent reply other threads:[~2001-12-27 11:53 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 [this message]
2002-01-02 4:34 ` Ralf Baechle
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=3C2AFD8C.6BAA7F1@mips.com \
--to=carstenl@mips.com \
--cc=jsun@mvista.com \
--cc=linux-mips@oss.sgi.com \
--cc=ralf@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