linux-mips
[Top] [All Lists]

Re: SoftFloat implementation for MIPS in GCC

To: Daniel Jacobowitz <dan@debian.org>
Subject: Re: SoftFloat implementation for MIPS in GCC
From: Jun Sun <jsun@mvista.com>
Date: Wed, 28 Jan 2004 11:53:12 -0800
Cc: Rajesh Palani <rpalani2@yahoo.com>, linux-mips@linux-mips.org, jsun@mvista.com
In-reply-to: <20040128193355.GA14318@nevyn.them.org>; from dan@debian.org on Wed, Jan 28, 2004 at 02:33:55PM -0500
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20040128192636.32578.qmail@web21603.mail.yahoo.com> <20040128193355.GA14318@nevyn.them.org>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.2.5i
On Wed, Jan 28, 2004 at 02:33:55PM -0500, Daniel Jacobowitz wrote:
> On Wed, Jan 28, 2004 at 11:26:36AM -0800, Rajesh Palani wrote:
> > Hi,
> >  
> >    We are using a gcc 2.96 20000731 (Red Hat Linux 7.1 2.96-99.1) GCC 
> > cross-compiler with -msoftfloat to use software floating point routines.
> >  
> >    When we profied an application using the Linux Trace Toolkit, we 
> > observed that  there were a lot of CpU (Co-processor unusable) exceptions.  
> > Some of the floating point routines ( eg. __floatdidf) expect values to be 
> > passed in floating point registers and take FP exceptions even though the 
> > application has been built with -msoftfloat.  Is this a general MIPS/GCC 
> > issue?  What is the status of softfloat  for MIPS in GCC?
> 
> Try a more recent compiler, that one is ancient.  If you configure
> correctly, you should get no references to the floating point registers
> at all.
> 

If glibc is not compiled with -msoftfloat, I think you will get a few
FPU exceptions from glibc no matter how apps are compiled.  

Actually, will it be a problem if glibc and apps are compiled differently
(such as in longjump, sig handling area)?

Jun

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