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


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

Re: [gcc] info req on long double support for PA


I've taken the liberty of cc:ing the gcc list to get this into the
archives - I hope you don't mind.

At 12:12 PM 10/12/99 -0700, enrico.musio wrote:

>You shouldn't say that ".. it appears that I'm the only one interested in
>Quad support on PA" :)

Glad to hear I'm not the only one. In various conversations with Jeff
Law about submitting and incorporating those changes to the HP-UX side
of things, I got the impression that no one from HP-UX had expressed
an interest in long double support. I don't have access to an HP-UX
box to test this, so I can sympathize with Jeff's not wanting to
incorporate them on anything other than MPE because it means more
work for him.

Let me know how your tests go.

>I hand-applied your patches to egcs-19991004 and they worked fine.
>(mail agent reformatting and release discrepancies didn't make patch happy)
I've been told that Eudora does tend to munge the patches. Next time
I'll tar them up for you.

>Have you any idea of when your contribution will be merged in a GCC release ?

It's really up to Jeff at this point. The MPE port is fairly low
priority and he's only been merging those things that don't affect the
other ports. Some of the files you need should already be there
(e.g. quadlib.asm). I'm waiting for the "go ahead" from
Jeff to submit the rest of the changes to pa.c, pa.h, pa.md and
some MPE specific files.

If your testing is successful, long double support could get
submitted separately from the MPE port. I'd be happy to repackage
and resubmit those at that time.

Regards,


M.
--
Mark Klein                                    DIS International, Ltd.
http://www.dis.com                            415-892-8400
PGP Public Key Available
--


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