This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] libstdc++ ABI issues with __int128
- From: Benjamin Kosnik <benjamin dot kosnik at gmail dot com>
- To: Jakub Jelinek <jakub at redhat dot com>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Sun, 20 Mar 2011 01:58:24 +0100
- Subject: Re: [PATCH] libstdc++ ABI issues with __int128
2011-03-19 Jakub Jelinek <jakub@redhat.com>
* config/abi/pre/gnu.ver (CXXABI_1.3): Don't export _ZT[IS][PK]*[no].
(CXXABI_1.3.5): Export _ZTI[PK]*[no].
This looks good to me, nice catch. I'll figure out what happened with
check_abi when I'm back, conductivity-wise.
And:
> And another question is, we still export a bunch of new _ZTS* symbols, isn't
> that now pointless when we always do strcmp anyway?
Yes, indeed it is as long as !__GXX_TYPEINFO_EQUALITY_INLINE &&
!__GXX_MERGED_TYPEINFO_NAMES for all targets that have baseline
symbols. I think that is correct, since they are all linux targets.
But arm-linux too?
> I'm talking about
> _ZTSSt16nested_exception@@CXXABI_1.3.5 OBJECT WEAK DEFAULT 21
> _ZTSNSt13__future_base11_State_baseE@@GLIBCXX_3.4.15 OBJECT WEAK DEFAULT 33
> _ZTSNSt13__future_base12_Result_baseE@@GLIBCXX_3.4.15 OBJECT WEAK DEFAULT 34
> _ZTSSt11regex_error@@GLIBCXX_3.4.15 OBJECT WEAK DEFAULT 16
> _ZTSSt12bad_weak_ptr@@GLIBCXX_3.4.15 OBJECT WEAK DEFAULT 17
> _ZTSSt17bad_function_call@@GLIBCXX_3.4.15 OBJECT WEAK DEFAULT 22
> here.
Yeah, basically all _ZTS* from GLIBCXX_3.4.15 and CXXABI_1.3.5 .
-benjamin