From: Daniel Jacobowitz <dan@debian.org>
To: Jun Sun <jsun@mvista.com>
Cc: Rajesh Palani <rpalani2@yahoo.com>, linux-mips@linux-mips.org
Subject: Re: SoftFloat implementation for MIPS in GCC
Date: Wed, 28 Jan 2004 15:00:44 -0500 [thread overview]
Message-ID: <20040128200044.GA15794@nevyn.them.org> (raw)
In-Reply-To: <20040128115312.B6210@mvista.com>
On Wed, Jan 28, 2004 at 11:53:12AM -0800, Jun Sun wrote:
> 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)?
Yes, that will be a problem. Nothing that takes or returns a floating
point value will work either.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2004-01-28 20:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-28 19:26 SoftFloat implementation for MIPS in GCC Rajesh Palani
2004-01-28 19:33 ` Daniel Jacobowitz
2004-01-28 19:53 ` Jun Sun
2004-01-28 19:57 ` David Daney
2004-01-28 20:00 ` Daniel Jacobowitz [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=20040128200044.GA15794@nevyn.them.org \
--to=dan@debian.org \
--cc=jsun@mvista.com \
--cc=linux-mips@linux-mips.org \
--cc=rpalani2@yahoo.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