This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: [PATCH] Add ABI baseline for s390x-*-linux*
- From: Ulrich Weigand <weigand at i1 dot informatik dot uni-erlangen dot de>
- To: doko at cs dot tu-berlin dot de (Matthias Klose)
- Cc: weigand at i1 dot informatik dot uni-erlangen dot de (Ulrich Weigand), bkoz at redhat dot com, libstdc++ at gcc dot gnu dot org, gt at debian dot org
- Date: Sun, 3 Oct 2004 02:37:19 +0200 (CEST)
- Subject: Re: [PATCH] Add ABI baseline for s390x-*-linux*
Matthias Klose wrote:
> Ulrich Weigand writes:
> > > Benjamin Kosnik wrote:
> > > > >Interestingly enough, the 3.4.0 baseline I built also has 7 symbols
> > > > >more than your version. I don't understand either why there's a
> > > > >difference ...
> > > >
> > > > Are the extra symbols similar to the ones referenced here:
> > > >
> > > > http://gcc.gnu.org/ml/libstdc++/2004-06/msg00269.html
> > >
> > > Yes, it's the exact same set.
> >
> > Any news on this issue? Is the patch OK now or should I do some
> > further investigations (which?)?
>
> If you have access to a Debian s390-linux chroot (sarge/unstable),
> please try to reproduce the results in this chroot. Maybe Gerhard Tonn
> could be helpful, I currently don't have access to s390-linux.
I don't have access to a Debian install currently, but I've downloaded
the sarge packages (libstdc++6_3.4.1-4sarge1_s390.deb etc.) and looked
at the binary images.
These look quite weird: the libstd++.a file contains the symbols
we're talking about, in the correct object io-inst.o. However,
the symbols are missing from the libstdc++.so shared library,
even though the *code* for the functions is in fact present in
the library, as evident from looking at the disassembly. The
entry point is simply not exported. (The package was stripped,
so I don't know whether the debug symbol would have been present
or not.)
In any case, according to the version script these symbols *should*
have been exported, and they are exported on my system, so at present
my guess would be some binutils issue on your build system ...
Bye,
Ulrich
--
Dr. Ulrich Weigand
weigand@informatik.uni-erlangen.de