This is the mail archive of the
mailing list for the GCC project.
Re: Backporting IA64 HP-UX patches to 4.2 and 4.1 branches
- From: Mark Mitchell <mark at codesourcery dot com>
- To: Steve Ellcey <sje at cup dot hp dot com>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Wed, 15 Nov 2006 13:36:48 -0800
- Subject: Re: Backporting IA64 HP-UX patches to 4.2 and 4.1 branches
- References: <200611152121.NAA03503@hpsje.cup.hp.com>
Steve Ellcey wrote:
> Mark Mitchell wrote:
>> I think the second is OK, but I'd prefer not to have the first (the
>> millicode stuff). That seems to have relatively small benefits, but
>> seems not without risk. If you feel strongly, let me know.
> I feel strongly.
OK, thanks for speaking up.
> if a
> user grabs one of these libraries (and that library includes an integer
> division) and then tries to link it in to his application using the HP
> compiler, he gets an uresolved reference to __divsi3 or __divdi3.
But hasn't it been this way forever? Has something changes that makes
this more pressing? Also, are these the only symbols we use from
libgcc? Can the user link with gcc instead of the HP compiler?
(650) 331-3385 x713