From: Jonathan Wakely <jwakely@redhat.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] libstdc++: Mention recent libgcc_s symbol versions in manual
Date: Wed, 3 May 2023 10:30:26 +0100 [thread overview]
Message-ID: <CACb0b4m=Y2B77isHmegzo4qwuOX7aKTpmK8yxxmbS+Wk=b96aA@mail.gmail.com> (raw)
In-Reply-To: <87h6sz66xx.fsf@oldenburg.str.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1284 bytes --]
On Fri, 28 Apr 2023 at 22:19, Florian Weimer via Libstdc++ <
libstdc++@gcc.gnu.org> wrote:
> GCC_11.0 is an aarch64-specific outlier.
>
> * doc/xml/manual/abi.xml (abi.versioning.history): Add
> GCC_7.0.0, GCC_9.0.0, GCC_11.0, GCC_12.0.0, GCC_13.0.0 for
> libgcc_s.
>
OK for trunk and gcc-13, thanks.
>
> ---
> libstdc++-v3/doc/xml/manual/abi.xml | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/libstdc++-v3/doc/xml/manual/abi.xml
> b/libstdc++-v3/doc/xml/manual/abi.xml
> index 3a3cbd3346c..e0e241de3bd 100644
> --- a/libstdc++-v3/doc/xml/manual/abi.xml
> +++ b/libstdc++-v3/doc/xml/manual/abi.xml
> @@ -203,6 +203,11 @@ compatible.
> <listitem><para>GCC 4.6.0: GCC_4.6.0</para></listitem>
> <listitem><para>GCC 4.7.0: GCC_4.7.0</para></listitem>
> <listitem><para>GCC 4.8.0: GCC_4.8.0</para></listitem>
> + <listitem><para>GCC 7.1.0: GCC_7.0.0</para></listitem>
> + <listitem><para>GCC 9.1.0: GCC_9.0.0</para></listitem>
> + <listitem><para>GCC 11.1.0: GCC_11.0</para></listitem>
> + <listitem><para>GCC 12.1.0: GCC_12.0.0</para></listitem>
> + <listitem><para>GCC 13.1.0: GCC_13.0.0</para></listitem>
> </itemizedlist>
> </listitem>
>
>
> base-commit: 0c77a0909456034d34036aa22a8dfcf0258cfa2d
>
>
prev parent reply other threads:[~2023-05-03 9:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 21:19 Florian Weimer
2023-05-03 9:30 ` 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='CACb0b4m=Y2B77isHmegzo4qwuOX7aKTpmK8yxxmbS+Wk=b96aA@mail.gmail.com' \
--to=jwakely@redhat.com \
--cc=fweimer@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--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).