This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Re: Calls to built-in functions are not Binary Compatible
- From: Tom Tromey <tromey at redhat dot com>
- To: Andrew Pinski <pinskia at physics dot uc dot edu>
- Cc: aph at redhat dot com (Andrew Haley), java-patches at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
- Date: 01 Mar 2006 15:31:01 -0700
- Subject: Re: Calls to built-in functions are not Binary Compatible
- References: <200603011833.k21IXT7B009360@earth.phy.uc.edu>
- Reply-to: tromey at redhat dot com
>>>>> "Andrew" == Andrew Pinski <pinskia@physics.uc.edu> writes:
>> This happens with methods like Math.pow() which are converted to
>> builtins. Unfortunately, this leads to direct calls to methods in
>> libgcj. This breaks binary compatibility when we change gcj's name
>> mangling. Which we just did.
Andrew> Aren't those direct function calls to libc functions though so
Andrew> they really don't have an effect from gcj's name mangling?
No, but some of these do lower to things which aren't function calls
at all. For instance take a look at how Double.longBitsToDouble is
handled.
Tom