This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: PATCH: ARM BPABI library routines
Richard Henderson wrote:
On Wed, Aug 11, 2004 at 07:49:27AM -0700, Mark Mitchell wrote:
I'm aware of the brokenness (we crash on some builtins, or with
flag_trapv) but I think that the crash is preferable to generating
non-compliant binaries.
Huh? "Non-compliant"? You don't think that if someone
uses __builtin_clzll they shouldn't get __clzdi2 from libgcc?
This argument makes no sense to me.
If they do, their application will not run on strict BPABI systems using
shared libraries.
The application may not assume that libgcc is around. For the most
part, the BPABI specifies the full set of routines that a compiler may
rely upon.
As a loophole, the BPABI allows applications to link special helper
routines (like __clzdi2) into generated object files as COMDAT, or to
provide a completely separate runtime library that contains only the
non-standard helper routines. The latter approach is probably what we
want to do for GCC in the medium term; for the BPABI, libgcc will be
split into a library containing just the BPABI routines and another
containing just the GCC-specific routines.
--
Mark Mitchell
CodeSourcery, LLC
(916) 791-8304
mark@codesourcery.com