public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Thomas Schwinge <tschwinge@baylibre.com>
To: Samuel Thibault <samuel.thibault@gnu.org>,
	Flavio Cruz <flaviocruz@gmail.com>,
	gcc-patches@gcc.gnu.org
Cc: bug-hurd@gnu.org
Subject: Re: [PATCH gcc] Hurd x86_64: add unwind support for signal trampoline code
Date: Wed, 20 Mar 2024 20:36:26 +0100	[thread overview]
Message-ID: <871q84puf9.fsf@euler.schwinge.ddns.net> (raw)
In-Reply-To: <20240301013310.rqpolnjwcxxqdtm6@begin>

Hi!

Please note that emails to <thomas.schwinge@siemens.com>, or
<thomas_schwinge@mentor.com> don't reach me anymore, and, at least for
the time being, likewise for <thomas@codesourcery.com> --
<tschwinge@baylibre.com> is the new thing; see
<https://baylibre.com/baylibre-expands-open-source-business-to-include-compiler-services/>.
(Or use <thomas@schwinge.name>, <tschwinge@gnu.org>,
<tschwinge@googlemail.com>, as before.)


On 2024-03-01T02:33:10+0100, Samuel Thibault <samuel.thibault@gnu.org> wrote:
> Flavio Cruz, le mer. 28 févr. 2024 22:59:09 -0500, a ecrit:
>> Tested with some simple toy examples where an exception is thrown in the
>> signal handler.
>> 
>> libgcc/ChangeLog:
>> 	* config/i386/gnu-unwind.h: Support unwinding x86_64 signal frames.
>> 
>> Signed-off-by: Flavio Cruz <flaviocruz@gmail.com>
>
> Reviewed-by: Samuel Thibault <samuel.thibault@ens-lyon.org>

Thanks, pushed as commit b7c4ae5ace82b81dafffbc50e8026adfa3cc76e7.


Grüße
 Thomas

      reply	other threads:[~2024-03-20 19:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-29  3:59 Flavio Cruz
2024-03-01  1:33 ` Samuel Thibault
2024-03-20 19:36   ` Thomas Schwinge [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=871q84puf9.fsf@euler.schwinge.ddns.net \
    --to=tschwinge@baylibre.com \
    --cc=bug-hurd@gnu.org \
    --cc=flaviocruz@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=samuel.thibault@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).