Re: how to find symbols needed for libgcc-compat in glibc
On Saturday 12 October 2002 19:48, Matthias Klose wrote:
> Jack Howarth writes:
> > Hi,
> > I am not filing a bug on this right now, but you should
> > all be aware that any arch that wants to switch to gcc 3.2
> > as its default compiler will need to address the following
> > issue. The libgcc symbols starting in gcc 3.1 are now .hidden
> > which means breakage of old binaries occurs when gcc 3.1/3.2
> > rebuilds glibc. Both ia64, in glibc trunk, and ppc, in glibc trunk
> > and glibc-2-2-branch, have this addressed. Franz and Jakub used
> > scripts to search for the list of symbols that needed to go
> > into the sysdeps/<arch>/libgcc-compat.S code. Jakub describes
> > this procedure as follows...
> what is the status of this list? Is this checked for all architectures
It's checked and o.k. on s390.