From: Matteo Italia <matteo@mitalia.net>
To: Jonathan Yong <10walls@gmail.com>, NightStrike <nightstrike@gmail.com>
Cc: 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: Wed, 7 Feb 2024 10:22:58 +0100 [thread overview]
Message-ID: <09006431-9e72-4573-98a5-123584c8526f@mitalia.net> (raw)
In-Reply-To: <82b90a96-99ce-4e9e-b4cc-11166b700327@gmail.com>
Il 06/02/24 10:17, Jonathan Yong ha scritto:
> On 2/6/24 05:31, NightStrike wrote:
>> On Mon, Feb 5, 2024, 06:53 Matteo Italia <matteo@mitalia.net> wrote:
>>
>>> Il 31/01/24 04:24, LIU Hao ha scritto:
>>>> 在 2024-01-31 08:08, Jonathan Yong 写道:
>>>>> On 1/24/24 15:17, Matteo Italia wrote:
>>>>>> Ping! That's a one-line fix, and you can find all the details in the
>>>>>> bugzilla entry. Also, I can provide executables built with the
>>>>>> affected toolchains, demonstrating the problem and the fix.
>>>>>>
>>>>>> Thanks,
>>>>>> Matteo
>>>>>>
>>>>>
>>>>> I was away last week. LH, care to comment? Changes look fine to me.
>>>>>
>>>>
>>>> The change looks good to me, too.
>>>>
>>>> I haven't tested it though. According to a similar construction around
>>>> 'libgcc/unwind.inc:265' it should be that way.
>>>
>>> Hello,
>>>
>>> thank you for the replies, is there anything else I can do to help push
>>> this forward?
>>>
>>
>> Remember to mention the pr with the right syntax in the ChangeLog so the
>> bot adds a comment field. I didn't see it in yours, but I might have
>> missed
>> it.
>>
>>>
>>
>
> Thanks all, pushed to master branch.
Thanks all :-) do you think this warrants backports? On one hand this is
a pretty niche feature, and I am probably the first to notice the
problem in ~12 years since that code was written, OTOH Win64/SEH was not
super widespread for a long time, and seems like a safe enough change.
Also: should I explicitly mark PR113337 as resolved? The bot added the
reference to the commit, but the PR is still marked as "UNCONFIRMED".
next prev parent reply other threads:[~2024-02-07 9:23 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 [this message]
2024-02-26 1:41 ` NightStrike
2024-02-26 12:12 ` Matteo Italia
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=09006431-9e72-4573-98a5-123584c8526f@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).