public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Matteo Italia <matteo@mitalia.net>
To: NightStrike <nightstrike@gmail.com>
Cc: Jonathan Yong <10walls@gmail.com>, LIU Hao <lh_mouse@126.com>,
	GCC Patches <gcc-patches@gcc.gnu.org>,
	tristan.gingold@cern.ch
Subject: Re: Ping: Re: [PATCH] libgcc: fix SEH C++ rethrow semantics [PR113337]
Date: Mon, 26 Feb 2024 13:12:28 +0100	[thread overview]
Message-ID: <1f43b588-3463-48c5-a401-3c7717a272e2@mitalia.net> (raw)
In-Reply-To: <CAF1jjLtNk7J-Wr3gYs4N6PCT8-8_+x8EH5C+Rj3=RZcSmNXXZA@mail.gmail.com>

Il 26/02/24 02:41, NightStrike ha scritto:
> It's mostly up to you whether you want to make the patch and test it.

I mean, the whole file has no code modifications since bd6ecbe48ada 
(2020), and that specific function is the same since it was first 
committed (bf1431e3596b, from 2012). I don't think I should make a 
separate patch for backports: the one I originally posted cherry-picks 
cleanly even to releases/gcc-4.8.0 (first release containing 
bf1431e3596b, at least according to git tag --contains), and the caller 
code is just the same as well, so I expect that technically it could be 
applied pretty much up to there without any modification.

Now, having a look at https://gcc.gnu.org/releases.html I seem to 
understand that the current "active" major releases are 11, 12 and 13. I 
would surely backport to 13, especially given that the patch was 
developed and tested on that release in first place. 11 and 12 would be 
nice too, although I made no explicit tests there; a quick check with

git diff releases/gcc-11.1.0 origin/master -- libgcc/unwind.inc 
libgcc/unwind-seh.c libstdc++-v3/libsupc++/eh_throw.cc

doesn't show any difference that is relevant for my patch. Still, if I 
find some time for that I could compile these patched releases and see 
if the patch still works correctly for extra caution.

Matteo


      reply	other threads:[~2024-02-26 12:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-17 11:51 Matteo Italia
2024-01-24 15:17 ` Ping: " Matteo Italia
2024-01-31  0:08   ` Jonathan Yong
2024-01-31  3:24     ` LIU Hao
2024-02-05 11:53       ` Matteo Italia
2024-02-06  5:31         ` NightStrike
2024-02-06  9:17           ` Jonathan Yong
2024-02-07  9:22             ` Matteo Italia
2024-02-26  1:41               ` NightStrike
2024-02-26 12:12                 ` Matteo Italia [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=1f43b588-3463-48c5-a401-3c7717a272e2@mitalia.net \
    --to=matteo@mitalia.net \
    --cc=10walls@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=lh_mouse@126.com \
    --cc=nightstrike@gmail.com \
    --cc=tristan.gingold@cern.ch \
    /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).