public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely@redhat.com>
To: Andreas Schwab <schwab@suse.de>
Cc: Jakub Jelinek <jakub@redhat.com>,
	libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] libstdc++: Regenerate trunk baseline_symbols.txt files for Linux
Date: Thu, 11 Apr 2024 15:48:46 +0100	[thread overview]
Message-ID: <CACb0b4n8v4LK1+QRzAB9KgQuNhRDCX3jhAm3u+ApyFBM_1KNEw@mail.gmail.com> (raw)
In-Reply-To: <mvmo7ag7y9p.fsf@suse.de>

On Thu, 11 Apr 2024 at 15:46, Andreas Schwab wrote:
>
> On Apr 11 2024, Jakub Jelinek wrote:
>
> > On Thu, Apr 11, 2024 at 04:35:52PM +0200, Andreas Schwab wrote:
> >> +FUNC:_ZNKSt12__shared_ptrINSt10filesystem28recursive_directory_iterator10_Dir_stackELN9__gnu_cxx12_Lock_policyE1EEcvbEv@@GLIBCXX_3.4.31
> >> +FUNC:_ZNKSt12__shared_ptrINSt10filesystem4_DirELN9__gnu_cxx12_Lock_policyE1EEcvbEv@@GLIBCXX_3.4.31
> >> +FUNC:_ZNKSt12__shared_ptrINSt10filesystem7__cxx1128recursive_directory_iterator10_Dir_stackELN9__gnu_cxx12_Lock_policyE1EEcvbEv@@GLIBCXX_3.4.31
> >> +FUNC:_ZNKSt12__shared_ptrINSt10filesystem7__cxx114_DirELN9__gnu_cxx12_Lock_policyE1EEcvbEv@@GLIBCXX_3.4.31
> >
> > If there are other changes needed for m68k, it means it wasn't regenerated
> > properly before the 13.1 release a year ago.
>
> Why do you think this has anything to do with m68k?


Looks like you were pointing out some missing lines for the
riscv64-linux-gnu baseline file, but Jakub's comment still applies.
That arch wasn't in Fedora, so wasn't in his r13-6532-gf875857e008c44
commit.

A riscv64-linux-gnu maintainer should have done that.


  reply	other threads:[~2024-04-11 14:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-11 14:17 Jakub Jelinek
2024-04-11 14:31 ` Jonathan Wakely
2024-04-11 14:35 ` Andreas Schwab
2024-04-11 14:39   ` Jakub Jelinek
2024-04-11 14:46     ` Andreas Schwab
2024-04-11 14:48       ` Jonathan Wakely [this message]
2024-04-11 14:40   ` 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=CACb0b4n8v4LK1+QRzAB9KgQuNhRDCX3jhAm3u+ApyFBM_1KNEw@mail.gmail.com \
    --to=jwakely@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@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).