From: Jonathan Wakely <jwakely@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: [PATCH] libstdc++: Some baseline_symbols.txt updates
Date: Tue, 7 Mar 2023 17:50:39 +0000 [thread overview]
Message-ID: <CACb0b4nL+Bjw5L+vyZNfowsOu-61tD0Qd2tS-iefZxxqQUaUfg@mail.gmail.com> (raw)
In-Reply-To: <Y/NfXD/wr0I7rmH9@tucnak>
On Mon, 20 Feb 2023 at 11:54, Jakub Jelinek via Libstdc++
<libstdc++@gcc.gnu.org> wrote:
>
> Hi!
Sorry for the delay.
> This updates baseline_symbols.txt for the Fedora 39 arches.
> Most of the added symbols are added to all 6 files, exceptions are
> DF16_ rtti stuff (only added on x86 and aarch64 which supports those),
> DF16b rtti stuff (only x86 right now), _M_replace_cold (m vs. j
> differences), DF128_ charconv (only x86), GLIBCXX_IEEE128_3.4.31
> symver symbols (only ppc64), GLIBCXX_LDBL_3.4.31 symver (ppc64 and s390x),
> _M_get_sys_info/_M_get_local_info (l vs. x) and
> 1 +FUNC:_ZSt15__try_use_facetINSt19__gnu_cxx11_ieee1289money_getIcSt19istreambuf_iteratorIcSt11char_traitsIcEEEEEPKT_RKSt6locale@@GLIBCXX_3.4.31
> 1 +FUNC:_ZSt15__try_use_facetINSt19__gnu_cxx11_ieee1289money_getIwSt19istreambuf_iteratorIwSt11char_traitsIwEEEEEPKT_RKSt6locale@@GLIBCXX_3.4.31
> 1 +FUNC:_ZSt15__try_use_facetINSt19__gnu_cxx11_ieee1289money_putIcSt19ostreambuf_iteratorIcSt11char_traitsIcEEEEEPKT_RKSt6locale@@GLIBCXX_3.4.31
> 1 +FUNC:_ZSt15__try_use_facetINSt19__gnu_cxx11_ieee1289money_putIwSt19ostreambuf_iteratorIwSt11char_traitsIwEEEEEPKT_RKSt6locale@@GLIBCXX_3.4.31
> for those, I wonder why they aren't in GLIBCXX_IEEE128_3.4.31 symver...
PR 108882 is fixed now, so they're not in the GLIBCXX_3.4.31 symver now.
> I was using
> grep ^+ | sed 's/OBJECT:[0-9]*:/OBJECT:/' | sort | uniq -c | sort -n | less
> on the patch to analyze.
>
> Ok for trunk?
I guess you want to regenerate the powerpc64 ones now. The others are
all OK for trunk.
>
> 2023-02-20 Jakub Jelinek <jakub@redhat.com>
>
> * config/abi/post/x86_64-linux-gnu/baseline_symbols.txt: Update.
> * config/abi/post/x86_64-linux-gnu/32/baseline_symbols.txt: Update.
> * config/abi/post/i486-linux-gnu/baseline_symbols.txt: Update.
> * config/abi/post/aarch64-linux-gnu/baseline_symbols.txt: Update.
> * config/abi/post/s390x-linux-gnu/baseline_symbols.txt: Update.
> * config/abi/post/powerpc64-linux-gnu/baseline_symbols.txt: Update.
next prev parent reply other threads:[~2023-03-07 17:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 11:54 Jakub Jelinek
2023-03-07 17:50 ` Jonathan Wakely [this message]
2023-03-13 9:10 ` [PATCH] libstdc++: Another baseline_symbols.txt update Jakub Jelinek
2023-03-13 10:27 ` 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=CACb0b4nL+Bjw5L+vyZNfowsOu-61tD0Qd2tS-iefZxxqQUaUfg@mail.gmail.com \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@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).