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 Linux
Date: Tue, 2 May 2023 17:50:17 +0200 [thread overview]
Message-ID: <ZFExOcUO3BN6X1Yl@tucnak> (raw)
In-Reply-To: <CACb0b4=tKm6z=65MrRcjogzoehvs-+-3=rUjvnLHSe72wXNXHw@mail.gmail.com>
On Tue, May 02, 2023 at 04:42:52PM +0100, Jonathan Wakely wrote:
> On Tue, 2 May 2023 at 09:45, Jakub Jelinek <jakub@redhat.com> wrote:
>
> > Hi!
> >
> > The following patch regenerates the ABI files (I've only changed the
> > Linux files which were updated recently (last month)).
> >
> > Tested on x86_64-linux, ok for trunk and later 13.2?
> >
>
> OK, thanks.
>
> I currently get:
> FAIL: libstdc++-abi/abi_check
> on powerpc64le for old glibc, with the _Float128 overloads for
> std::from_chars and std::to_chars.
I'll try to regenerate it from latest Fedora build for ppc64le.
> Those symbols were OK when GLIBCXX_3.4.31 was the latest, because added
> symbols in the latest version are OK. Now that GLIBCXX_3.4.32 is the
> latest, we can't have additions to the older version.
Jakub
next prev parent reply other threads:[~2023-05-02 15:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-02 8:45 Jakub Jelinek
2023-05-02 15:42 ` Jonathan Wakely
2023-05-02 15:50 ` Jakub Jelinek [this message]
2023-05-02 17:32 ` Jakub Jelinek
2024-04-11 13:51 Jakub Jelinek
2024-04-11 13:53 ` Jonathan Wakely
2024-04-11 14:11 ` 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=ZFExOcUO3BN6X1Yl@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).