This is the mail archive of the
mailing list for the libstdc++ project.
RE: Irix6 long doubles implemented wrong? (27_io/ostream_inserter_arith)
- From: "Billinghurst, David (CRTS)" <David dot Billinghurst at riotinto dot com>
- To: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>,<aoliva at redhat dot com>
- Cc: <gcc at gcc dot gnu dot org>,<libstdc++ at gcc dot gnu dot org>
- Date: Tue, 17 Dec 2002 16:39:05 +1100
- Subject: 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.
From: Kaveh R. Ghazi [mailto:email@example.com]
Sent: Tuesday, 17 December 2002 4:32 PM
Cc: firstname.lastname@example.org; email@example.com; firstname.lastname@example.org;
Subject: Re: Irix6 long doubles implemented wrong?
> From: Alexandre Oliva <email@example.com>
> On Dec 14, 2002, "Kaveh R. Ghazi" <firstname.lastname@example.org> 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.
Considering the current irix libc incompatibility, one cannot
currently input or output long doubles using stdio. What good is
I definitely support fixing the ABI, perhaps even on the 3.3 branch if
the patch is not too invasive.
Kaveh R. Ghazi email@example.com