PATCH: Don't export libgcc symbol (Re: symbol clarification please?)

Franz Sirl Franz.Sirl-kernel@lauterbach.com
Tue Aug 13 08:44:00 GMT 2002


At 17:29 13.08.2002, H. J. Lu wrote:
>On Tue, Aug 13, 2002 at 01:08:11AM -0400, Jack Howarth wrote:
> > Ulrich,
> >     Okay, after talking to HJ, if I understand him correctly,
> > if a symbol appears as it does now in glibc-2-2-branch on ppc
> > as...
> >
> > 000266b0 g    DF .text        000000c8  GLIBC_2.0   __divdi3
> >
> > ...this exports the symbol for linking as well as
> > for run-time resolution. Now my understanding was
> > that you demanded we not export the symbols from
> > libgcc-compat for linking. Franz's revised patch
> > appears to do exactly this with this result instead...
> >
> > 00026680 g    DF .text        000000c8 (GLIBC_2.0)  __divdi3
> >
>
>The invasive patch for glibc 2.2 is not my taste. Also I prefer C over
>assembly. Please try this on glibc 2.2.

The assembly is used for optimization, to avoid typos in parameter passing 
and to tell the linker it can use a local jump (@local).

Besides that, your patch has the same problem as mine, it will break 
building of gcc-3, these 4 symbols will no longer be versioned then in 
libgcc_s (just try building gcc-3.2 on entropy, which has a glibc with a 
similar patch installed). That's the whole reason I didn't submit the patch 
yet, cause if the GCC people don't accept the patch, the glibc patch can't 
be applied either.

Franz.



More information about the Libc-alpha mailing list