From: Andreas Jaeger <aj@suse.de>
To: Jun Sun <jsun@mvista.com>
Cc: "Kevin D. Kissell" <kevink@mips.com>,
Florian Lohoff <flo@rfc822.org>,
linux-mips@oss.sgi.com
Subject: Re: [RESUME] fpu emulator
Date: 09 Feb 2001 10:17:05 +0100 [thread overview]
Message-ID: <hoae7wjjvy.fsf@gee.suse.de> (raw)
In-Reply-To: <3A8304C0.D3CFFEF7@mvista.com> (Jun Sun's message of "Thu, 08 Feb 2001 12:42:40 -0800")
Jun Sun <jsun@mvista.com> writes:
> Andreas Jaeger wrote:
> >
>
> > > saves/restores the FP registers in setjmp/longjmp, the
> >
> > Any ideas how this can be done?
> >
> > > model of "simply sending SIGILL/SIGFPE" will result
> > > in *all* processes being terminated with extreme prejudice,
> > > starting with init!
> >
>
> There is a patch for glibc2.0.7, which I think was done by Jay Carlson. It
> basically works for glibc2.0.6 as well. See the one for glibc2.0.6 attached
> below.
>
> I think the patch is not "clean", in the sense that you only want to apply it
> if you want to configure with "--without-fp". Otherwise the patch will break
> other configurations.
>
> Jun--- glibc-2.0.6/sysdeps/mips/__longjmp.c.orig-rpm Sat Sep 11 00:01:44 1999
> +++ glibc-2.0.6/sysdeps/mips/__longjmp.c Sat Sep 11 00:02:36 1999
> @@ -35,6 +35,7 @@
> along the way. */
> register int val asm ("a1");
>
> +#ifdef __HAVE_FPU__
I looked through the whole of glibc and GCC and __HAVE_FPU__ is nowhere
defined for MIPS. __HAVE_FPU__ is defined for m68k in GCC but that's
the only platform.
Therefore I don't think the patch makes any sense at all,
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
next prev parent reply other threads:[~2001-02-09 9:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-08 11:20 [RESUME] fpu emulator Florian Lohoff
2001-02-08 11:43 ` Kevin D. Kissell
2001-02-08 11:43 ` Kevin D. Kissell
2001-02-08 12:06 ` Andreas Jaeger
2001-02-08 12:06 ` Andreas Jaeger
2001-02-08 20:42 ` Jun Sun
2001-02-09 9:17 ` Andreas Jaeger [this message]
2001-02-09 19:30 ` Jun Sun
2001-02-09 20:31 ` Andreas Jaeger
2001-02-09 21:09 ` Jun Sun
2001-02-08 12:33 ` Florian Lohoff
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=hoae7wjjvy.fsf@gee.suse.de \
--to=aj@suse.de \
--cc=flo@rfc822.org \
--cc=jsun@mvista.com \
--cc=kevink@mips.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