From: Jakub Jelinek <jakub@redhat.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: Andreas Schwab <schwab@suse.de>,
libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] libstdc++: Regenerate baseline_symbols.txt files for Linux
Date: Thu, 11 Apr 2024 16:18:31 +0200 [thread overview]
Message-ID: <ZhfxN7RBrvQhW5YU@tucnak> (raw)
In-Reply-To: <CACb0b4=rb4NfJ3RLib101ZeCSKSCX3GAdC2KEzVtno_ChfjYRQ@mail.gmail.com>
On Thu, Apr 11, 2024 at 03:16:02PM +0100, Jonathan Wakely wrote:
> > That symbol should not be in this symver, see
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114692 and
> > https://gcc.gnu.org/pipermail/gcc-patches/2024-April/649260.html
>
> Jakub's patch is just adding the symbols from gcc-13.2.0 which should
> be in the baselines for both gcc-13 and trunk.
Yes.
> After that's done I can fix PR114692 and then we can regen the
> baselines for trunk, which will include the
> __cxa_call_terminate@@CXXABI_1.3.15 symbol, but also have
> _ZNKSt12__basic_fileIcE13native_handleEv@@GLIBCXX_3.4.33 (N.B. 3.4.33
> not 3.4.32).
I've already posted that.
Jakub
next prev parent reply other threads:[~2024-04-11 14:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 13:51 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
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-02 8:45 Jakub Jelinek
2023-05-02 15:42 ` Jonathan Wakely
2023-05-02 15:50 ` Jakub Jelinek
2023-05-02 17:32 ` 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=ZhfxN7RBrvQhW5YU@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely@redhat.com \
--cc=libstdc++@gcc.gnu.org \
--cc=schwab@suse.de \
/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).