linux-mips
[Top] [All Lists]

Re: MIPS SF toolchain

To: Matej Kupljen <matej.kupljen@ultra.si>
Subject: Re: MIPS SF toolchain
From: Ralf Baechle <ralf@linux-mips.org>
Date: Thu, 8 Sep 2005 13:29:33 +0100
Cc: David Daney <ddaney@avtrex.com>, crossgcc@sources.redhat.com, linux-mips@linux-mips.org
In-reply-to: <1126182122.25393.27.camel@orionlinux.starfleet.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <1126098584.12696.19.camel@localhost.localdomain> <431F0850.8090804@avtrex.com> <1126168866.25388.11.camel@orionlinux.starfleet.com> <1126179199.25389.20.camel@orionlinux.starfleet.com> <1126182122.25393.27.camel@orionlinux.starfleet.com>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.4.2.1i
On Thu, Sep 08, 2005 at 02:22:02PM +0200, Matej Kupljen wrote:

> > and
> > -------------------------------------------------------------
> > 0002ff70 <__sigsetjmp_aux>:
> >    2ff70:       3c1c0017        lui     gp,0x17
> >    2ff74:       279cce40        addiu   gp,gp,-12736
> 
> This code is written in sysdeps/mips/__longjmp.c in 
> inline assembly.
> 
> > How to solve this?
> 
> Because I am using sf, there is no need to store those
> registers, or is it?
> Can I just #ifdef this code if compiled for sf?

Why not just letting the kernel fp emulator do the job?  On the average
fpu-less system fp performance doesn't matter, so the impact of the
kernel fp emulator is much less than the pain of avoiding it.

  Ralf

<Prev in Thread] Current Thread [Next in Thread>