This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: Irix6 long doubles implemented wrong? (27_io/ostream_inserter_arith)


I'd prefer that it was correct, even if this means breaking the gcc ABI.

-----Original Message-----
From: Kaveh R. Ghazi [mailto:ghazi@caip.rutgers.edu]
Sent: Tuesday, 17 December 2002 4:32 PM
To: aoliva@redhat.com
Cc: gcc-bugs@gcc.gnu.org; gcc@gcc.gnu.org; libstdc++@gcc.gnu.org;
oldham@codesourcery.com; ro@TechFak.Uni-Bielefeld.DE
Subject: Re: Irix6 long doubles implemented wrong?
(27_io/ostream_inserter_arith)


 > From: Alexandre Oliva <aoliva@redhat.com>
 > 
 > On Dec 14, 2002, "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu> wrote:
 > 
 > > Does anyone have any thoughts on this?  (Or better yet a fix?)
 > 
 > I've been working on a patch that will enable us to switch to 128-bit
 > long doubles on mips n32 and n64, but I still need a little bit of
 > polishing and checking (I know that my current patch still doesn't
 > pass long double arguments in the right registers).  I expect to have
 > it finished in the next few days.

Excellent!  Let me know if I can be of service testing your patch.


 > That said, I'm not sure it would be wise to break the gcc ABI on IRIX
 > 6 by introducing this change.  It's not like long double is the most
 > widely used type, but still, I'm a bit concerned about changing it.
 > Opinions?

Considering the current irix libc incompatibility, one cannot
currently input or output long doubles using stdio.  What good is
that? :-)

I definitely support fixing the ABI, perhaps even on the 3.3 branch if
the patch is not too invasive.

		Thanks,
		--Kaveh
--
Kaveh R. Ghazi			ghazi@caip.rutgers.edu


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]