public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Jonathan Wakely <jwakely@redhat.com>,
	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 19:32:49 +0200	[thread overview]
Message-ID: <ZFFJQXz6NoMK5xw4@tucnak> (raw)
In-Reply-To: <ZFExOcUO3BN6X1Yl@tucnak>

On Tue, May 02, 2023 at 05:50:17PM +0200, Jakub Jelinek via Gcc-patches wrote:
> 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.

Strange.  The powerpc64-linux right before my commit matches exactly
Fedora 39 13.1.1 ppc64le build (except the usual 2 TLS lines).

	Jakub


  reply	other threads:[~2023-05-02 17:32 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
2023-05-02 17:32     ` Jakub Jelinek [this message]
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=ZFFJQXz6NoMK5xw4@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).