On Wed, Jan 28, 2004 at 02:33:55PM -0500, Daniel Jacobowitz wrote:I have found that some versions of glibc (2.2.5 for example) have hard coded floating point code (in longjump handling IIRC) so no matter what you do you get the exceptions.
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)?
David Daney.
