From: "François Dumont" <frs.dumont@gmail.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: "libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Add missing gnu-versioned-namespace symbols
Date: Mon, 2 Nov 2020 21:52:36 +0100 [thread overview]
Message-ID: <9c81c091-497e-2e36-a855-ce88fc91fdf9@gmail.com> (raw)
In-Reply-To: <20201102141735.GS503596@redhat.com>
On 02/11/20 3:17 pm, Jonathan Wakely wrote:
> On 01/11/20 20:48 +0100, François Dumont via Libstdc++ wrote:
>> Several tests are failing because of those missing symbols.
>>
>> I understand why we need to export symbols relying in the versioned
>> namespace but I don't understand why we need to do it for
>> _GLIBCXX_DEBUG symbols which are not version namespace dependant.
>
> If you don't export the symbol, it can't be found by code linking to
> libstdc++.so.8
So I understand that in versioned namespace mode only
gnu-versioned-namespace.ver is being used and not gnu.ver.
>
> This linker script is the only one used to build libstdc++.so.8 so all
> symbols that need to be exported by that library have to be exported
> by this script. Nothing exports that debug symbol unless you add it
> here.
>
> What I don't understand is why the __istream_extract symbol isn't
> matched by the wildcard in the extern "C++" block at the top of the
> file.
Maybe for the same reason that the std::__copy_streambufs before this
one and some others symbols in std::__8 had to be explicitely exported too.
But I don't know it.
>
>> Do you want to backport the Debug symbol ?
>>
>> Â Â Â libstdc++: Add mising gnu-versioned-namespace symbols
>>
>> Â Â Â libstdc++-v3/ChangeLog:
>>
>> Â Â Â Â Â Â Â Â Â Â Â * config/abi/pre/gnu-versioned-namespace.ver:
>> Â Â Â Â Â Â Â Â Â Â Â Add __istream_extract and
>> _Safe_local_iterator_base::_M_attach_single
>> Â Â Â Â Â Â Â Â Â Â Â symbols.
>>
>> Tested under Linux x86_64 versioned namespace.
>>
>> Ok to commit ?
>>
>> François
>>
>
>> diff --git a/libstdc++-v3/config/abi/pre/gnu-versioned-namespace.ver
>> b/libstdc++-v3/config/abi/pre/gnu-versioned-namespace.ver
>> index 0965854fbc3..3b6d7944d06 100644
>> --- a/libstdc++-v3/config/abi/pre/gnu-versioned-namespace.ver
>> +++ b/libstdc++-v3/config/abi/pre/gnu-versioned-namespace.ver
>> @@ -98,6 +98,9 @@ GLIBCXX_8.0 {
>> _ZNSt3__817__copy_streambufsI*;
>> _ZNSt3__821__copy_streambufs_eofI*;
>>
>> + # std::__istream_extract(wistream&, wchar_t*, streamsize)
>> +
>> _ZNSt3__817__istream_extractIwNS_11char_traitsIwEEEEvRNS_13basic_istreamIT_T0_EEPS4_[ilx];
>> +
>> # __gnu_cxx::__atomic_add
>> # __gnu_cxx::__exchange_and_add
>> _ZN9__gnu_cxx3__812__atomic_addEPV[il][il];
>> @@ -145,6 +148,7 @@ GLIBCXX_8.0 {
>> _ZN11__gnu_debug30_Safe_unordered_container_base13_M_detach_allEv;
>> _ZN11__gnu_debug25_Safe_local_iterator_base9_M_attachEPNS_19_Safe_sequence_baseEb;
>> _ZN11__gnu_debug25_Safe_local_iterator_base9_M_detachEv;
>> +
>> _ZN11__gnu_debug25_Safe_local_iterator_base16_M_attach_singleEPNS_19_Safe_sequence_baseEb;
>>
>> # parallel mode
>> _ZN14__gnu_parallel9_Settings3getEv;
>
next prev parent reply other threads:[~2020-11-02 20:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-01 19:48 François Dumont
2020-11-02 14:17 ` Jonathan Wakely
2020-11-02 20:52 ` François Dumont [this message]
2020-11-03 8:25 ` Jonathan Wakely
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9c81c091-497e-2e36-a855-ce88fc91fdf9@gmail.com \
--to=frs.dumont@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely@redhat.com \
--cc=libstdc++@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).