public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Patrick Palka <ppalka@redhat.com>,
	gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org,
	 Rainer Orth <ro@cebitec.uni-bielefeld.de>
Subject: Re: [PATCH] libstdc++: Another attempt to ensure g++ 13+ compiled programs enforce gcc 13.2+ libstdc++.so.6 [PR108969]
Date: Tue, 2 May 2023 16:43:23 +0100	[thread overview]
Message-ID: <CACb0b4nfUeBrAP4X8SWCuz8tDN3g3sYYbBfDMwe2cjdmhvYR1Q@mail.gmail.com> (raw)
In-Reply-To: <ZExCYpOBBHjLNkqf@tucnak>

[-- Attachment #1: Type: text/plain, Size: 936 bytes --]

On Fri, 28 Apr 2023 at 23:02, Jakub Jelinek <jakub@redhat.com> wrote:

> On Fri, Apr 28, 2023 at 09:35:49AM +0100, Jonathan Wakely wrote:
> > Yes, for both, thanks for the fix.
> >
> > After it lands on the gcc-13 branch I'll also update the manual with:
> >
> > --- a/libstdc++-v3/doc/xml/manual/abi.xml
> > +++ b/libstdc++-v3/doc/xml/manual/abi.xml
> > @@ -275,6 +275,7 @@ compatible.
> >     <listitem><para>GCC 11.1.0: libstdc++.so.6.0.29</para></listitem>
> >     <listitem><para>GCC 12.1.0: libstdc++.so.6.0.30</para></listitem>
> >     <listitem><para>GCC 13.1.0: libstdc++.so.6.0.31</para></listitem>
> > +    <listitem><para>GCC 13.2.0: libstdc++.so.6.0.32</para></listitem>
> >     </itemizedlist>
> >     <para>
> >       Note 1: Error should be libstdc++.so.3.0.3.
>
> Don't you need to change later parts too?
> I mean adding
>   GCC 13.2.0: GLIBCXX_3.4.32, CXXABI_1.3.14
> entry.
>

Yep, and regenerate the HTML versions.

  reply	other threads:[~2023-05-02 15:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-28  7:34 Jakub Jelinek
2023-04-28  8:35 ` Jonathan Wakely
2023-04-28 22:02   ` Jakub Jelinek
2023-05-02 15:43     ` Jonathan Wakely [this message]
2023-05-02 11:20 ` Rainer Orth

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=CACb0b4nfUeBrAP4X8SWCuz8tDN3g3sYYbBfDMwe2cjdmhvYR1Q@mail.gmail.com \
    --to=jwakely@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=libstdc++@gcc.gnu.org \
    --cc=ppalka@redhat.com \
    --cc=ro@cebitec.uni-bielefeld.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).