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:40:05 +0100	[thread overview]
Message-ID: <CACb0b4ntpfZfRJyVAN2SyuLODpUBvGKd623CSWruXs+yk4+_Qg@mail.gmail.com> (raw)
In-Reply-To: <mvmsezs7yrb.fsf@suse.de>

On Thu, 11 Apr 2024 at 15:36, Andreas Schwab <schwab@suse.de> wrote:
>
> On Apr 11 2024, Jakub Jelinek wrote:
>
> > --- libstdc++-v3/config/abi/post/riscv64-linux-gnu/baseline_symbols.txt.jj    2024-04-11 15:55:49.982325397 +0200
> > +++ libstdc++-v3/config/abi/post/riscv64-linux-gnu/baseline_symbols.txt       2024-04-11 16:10:05.206559463 +0200
> > @@ -497,6 +497,7 @@ FUNC:_ZNKSt11__timepunctIwE7_M_daysEPPKw
> >  FUNC:_ZNKSt11__timepunctIwE8_M_am_pmEPPKw@@GLIBCXX_3.4
> >  FUNC:_ZNKSt11__timepunctIwE9_M_monthsEPPKw@@GLIBCXX_3.4
> >  FUNC:_ZNKSt11logic_error4whatEv@@GLIBCXX_3.4
> > +FUNC:_ZNKSt12__basic_fileIcE13native_handleEv@@GLIBCXX_3.4.33
> >  FUNC:_ZNKSt12__basic_fileIcE7is_openEv@@GLIBCXX_3.4
> >  FUNC:_ZNKSt12bad_weak_ptr4whatEv@@GLIBCXX_3.4.15
> >  FUNC:_ZNKSt12future_error4whatEv@@GLIBCXX_3.4.14
> > @@ -4525,6 +4526,7 @@ FUNC:__cxa_allocate_exception@@CXXABI_1.
> >  FUNC:__cxa_bad_cast@@CXXABI_1.3
> >  FUNC:__cxa_bad_typeid@@CXXABI_1.3
> >  FUNC:__cxa_begin_catch@@CXXABI_1.3
> > +FUNC:__cxa_call_terminate@@CXXABI_1.3.15
> >  FUNC:__cxa_call_unexpected@@CXXABI_1.3
> >  FUNC:__cxa_current_exception_type@@CXXABI_1.3
> >  FUNC:__cxa_deleted_virtual@@CXXABI_1.3.6
> > @@ -4568,6 +4570,7 @@ OBJECT:0:CXXABI_1.3.11
> >  OBJECT:0:CXXABI_1.3.12
> >  OBJECT:0:CXXABI_1.3.13
> >  OBJECT:0:CXXABI_1.3.14
> > +OBJECT:0:CXXABI_1.3.15
> >  OBJECT:0:CXXABI_1.3.2
> >  OBJECT:0:CXXABI_1.3.3
> >  OBJECT:0:CXXABI_1.3.4
> > @@ -4604,6 +4607,7 @@ OBJECT:0:GLIBCXX_3.4.3
> >  OBJECT:0:GLIBCXX_3.4.30
> >  OBJECT:0:GLIBCXX_3.4.31
> >  OBJECT:0:GLIBCXX_3.4.32
> > +OBJECT:0:GLIBCXX_3.4.33
> >  OBJECT:0:GLIBCXX_3.4.4
> >  OBJECT:0:GLIBCXX_3.4.5
> >  OBJECT:0:GLIBCXX_3.4.6
>
> +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


Ah yes, looks like these were added for other arches in
r13-6532-gf875857e008c44 but that didn't include riscv64-linux


      parent reply	other threads:[~2024-04-11 14:40 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
2024-04-11 14:40   ` Jonathan Wakely [this message]

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=CACb0b4ntpfZfRJyVAN2SyuLODpUBvGKd623CSWruXs+yk4+_Qg@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).