From: Jonathan Wakely <jwakely@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Richard Biener <richard.guenther@gmail.com>,
Jason Merrill <jason@redhat.com>,
gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: [PATCH RFC] c++: use __cxa_call_terminate for MUST_NOT_THROW [PR97720]
Date: Fri, 9 Jun 2023 13:15:13 +0100 [thread overview]
Message-ID: <CACb0b4=y3JuG_t_9EWPY_bT0KJv-pOQwFK6uDzOCtfsKWgn+3w@mail.gmail.com> (raw)
In-Reply-To: <ZILsOCLIJs6GMheA@tucnak>
[-- Attachment #1: Type: text/plain, Size: 1023 bytes --]
On Fri, 9 Jun 2023 at 10:09, Jakub Jelinek <jakub@redhat.com> wrote:
> On Fri, Jun 09, 2023 at 11:02:48AM +0200, Richard Biener via Gcc-patches
> wrote:
> > > Currently both gcc-13 and trunk are at the same library version,
> > > libstdc++.so.6.0.32
> > >
> > > But with this addition to trunk we need to bump that .32 to .33,
> meaning
> > > that gcc-13 and trunk diverge. If we want to backport any new symbols
> from
> > > trunk to gcc-13 that gets trickier once they've diverged.
> >
> > But if you backport any new used symbol you have to bump the version
> > anyway. So why not bump now (on trunk)?
>
> We've already done that in 13.1.1. So, before 13.2 is released, we can add
> further symbols to the GLIBCXX_3.4.32 symbol version.
> Though, I don't see a problem bumping libstdc++ to libstdc++.so.6.0.33
> on the trunk now
OK, done at r14-1649-g9a3558cf1fb40b
> and put __cxa_call_terminate to GLIBCXX_3.4.33.
>
Well it's already in CXXABI_1.3.15, we just didn't bump the library version
when adding that.
next prev parent reply other threads:[~2023-06-09 12:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 18:55 Jason Merrill
2023-05-26 9:58 ` Jonathan Wakely
2023-06-08 13:13 ` Jonathan Wakely
2023-06-08 14:03 ` Jason Merrill
2023-06-09 9:02 ` Richard Biener
2023-06-09 9:06 ` Jonathan Wakely
2023-06-09 9:09 ` Jakub Jelinek
2023-06-09 12:15 ` Jonathan Wakely [this message]
2023-06-02 16:56 ` PING Re: [PATCH RFA (tree-eh)] " Jason Merrill
2023-06-05 6:09 ` Richard Biener
2023-06-05 19:10 ` Jason Merrill
2023-06-03 14:33 ` [PATCH RFC] " Jeff Law
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='CACb0b4=y3JuG_t_9EWPY_bT0KJv-pOQwFK6uDzOCtfsKWgn+3w@mail.gmail.com' \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=jason@redhat.com \
--cc=libstdc++@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
/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).