This is the mail archive of the libc-hacker@sources.redhat.com mailing list for the glibc project.

Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.


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

Re: My proposal for the libgcc runtime ABI (ia64 gcc/glibc is broken.)


"Martin v. Loewis" <martin@loewis.home.cs.tu-berlin.de> writes:

> If you think you (as the glibc group, or as the Ulrich Drepper
> individual) can maintain this over the years to come - why don't you
> just go ahead and do it?

I've never said I want to do this.  I have enough to do.

> It is likely that gcc maintainers will add functions to libgcc as they
> please, and that the code generated by gcc will rely on these
> functions being inside libgcc. So how should gcc proceed on a system
> where these new functions are not present in the system libgcc?

The libgcc ABI cannot simply be changed without good reason and
preparation.  This should be clear meanwhile.  There must be much
finer coordination.

-- 
---------------.                          ,-.   1325 Chesapeake Terrace
Ulrich Drepper  \    ,-------------------'   \  Sunnyvale, CA 94089 USA
Red Hat          `--' drepper at redhat.com   `------------------------

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