From: Jakub Jelinek <jakub@redhat.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] libstdc++: Regenerate baseline_symbols.txt files for i386-linux-gnu
Date: Thu, 11 Apr 2024 16:06:34 +0200 [thread overview]
Message-ID: <ZhfuaimOYd/0PABA@tucnak> (raw)
In-Reply-To: <20240411135929.521941-1-jwakely@redhat.com>
On Thu, Apr 11, 2024 at 02:59:05PM +0100, Jonathan Wakely wrote:
> I think we also want the same change for i386.
>
> -- >8 --
>
> libstdc++-v3/ChangeLog:
>
> * config/abi/post/i386-linux-gnu/baseline_symbols.txt:
> Regenerate.
Not sure about that, the file is missing all the 3.4.30, 3.4.31 and other
3.4.32 symbols as well.
It needs to be regenerated.
I'm not really sure what i386 really is and if we support it at all, given
that it doesn't support the fundamental locking instructions.
> --- a/libstdc++-v3/config/abi/post/i386-linux-gnu/baseline_symbols.txt
> +++ b/libstdc++-v3/config/abi/post/i386-linux-gnu/baseline_symbols.txt
> @@ -3186,6 +3186,7 @@ FUNC:_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE10_M_disposeEv@@GLIBCX
> FUNC:_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE10_M_replaceEjjPKcj@@GLIBCXX_3.4.21
> FUNC:_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE10_S_compareEjj@@GLIBCXX_3.4.21
> FUNC:_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE11_M_capacityEj@@GLIBCXX_3.4.21
> +FUNC:_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE11_S_allocateERS3_j@@GLIBCXX_3.4.32
> FUNC:_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_Alloc_hiderC1EPcOS3_@@GLIBCXX_3.4.23
> FUNC:_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_Alloc_hiderC1EPcRKS3_@@GLIBCXX_3.4.21
> FUNC:_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_Alloc_hiderC2EPcOS3_@@GLIBCXX_3.4.23
> @@ -3337,6 +3338,7 @@ FUNC:_ZNSt7__cxx1112basic_stringIwSt11char_traitsIwESaIwEE10_M_disposeEv@@GLIBCX
> FUNC:_ZNSt7__cxx1112basic_stringIwSt11char_traitsIwESaIwEE10_M_replaceEjjPKwj@@GLIBCXX_3.4.21
> FUNC:_ZNSt7__cxx1112basic_stringIwSt11char_traitsIwESaIwEE10_S_compareEjj@@GLIBCXX_3.4.21
> FUNC:_ZNSt7__cxx1112basic_stringIwSt11char_traitsIwESaIwEE11_M_capacityEj@@GLIBCXX_3.4.21
> +FUNC:_ZNSt7__cxx1112basic_stringIwSt11char_traitsIwESaIwEE11_S_allocateERS3_j@@GLIBCXX_3.4.32
> FUNC:_ZNSt7__cxx1112basic_stringIwSt11char_traitsIwESaIwEE12_Alloc_hiderC1EPwOS3_@@GLIBCXX_3.4.23
> FUNC:_ZNSt7__cxx1112basic_stringIwSt11char_traitsIwESaIwEE12_Alloc_hiderC1EPwRKS3_@@GLIBCXX_3.4.21
> FUNC:_ZNSt7__cxx1112basic_stringIwSt11char_traitsIwESaIwEE12_Alloc_hiderC2EPwOS3_@@GLIBCXX_3.4.23
> --
> 2.44.0
Jakub
next prev parent reply other threads:[~2024-04-11 14:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 13:51 [PATCH] libstdc++: Regenerate baseline_symbols.txt files for Linux Jakub Jelinek
2024-04-11 13:53 ` Jonathan Wakely
2024-04-11 13:59 ` [PATCH] libstdc++: Regenerate baseline_symbols.txt files for i386-linux-gnu Jonathan Wakely
2024-04-11 14:06 ` Jakub Jelinek [this message]
2024-04-11 14:07 ` Jonathan Wakely
2024-04-11 14:11 ` [PATCH] libstdc++: Regenerate baseline_symbols.txt files for Linux Andreas Schwab
2024-04-11 14:13 ` Jonathan Wakely
2024-04-11 14:16 ` Jonathan Wakely
2024-04-11 14:18 ` Jakub Jelinek
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=ZhfuaimOYd/0PABA@tucnak \
--to=jakub@redhat.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).