From: Kai Tietz <ktietz70@googlemail.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Cc: "libstdc++" <libstdc++@gcc.gnu.org>
Subject: Re: [patch libstdc++]: Fix PR target/55445 Always defined __SEH__ when build from trunk
Date: Wed, 28 Nov 2012 18:02:00 -0000 [thread overview]
Message-ID: <CAEwic4aPP130S1vTrqTUJTsB0T=zPD0-nnSm4obyVKTsSi_XpQ@mail.gmail.com> (raw)
In-Reply-To: <CAEwic4ZWF14Jigg1BPzFd6QmQZgBR8bwMu2ezxJRUVV4OKDkdw@mail.gmail.com>
Ping
2012/11/25 Kai Tietz <ktietz70@googlemail.com>:
> Hi,
>
> this patch fixes used exception-mechanism for SEH-enabled targets,
> which are requesting for SjLj-exception-mechanism.
> See also patch for libgcc.
>
> ChangeLog
>
> 2012-11-25 Kai Tietz
>
> PR target/55445
> * libsupc++/eh_personaltity.cc (__SEH__): Additional check
> for not being SjLj.
>
> Tested for multilib i686-w64-mingw32, and x86_64-w64-mingw32 targets.
> Ok for apply?
>
> Regards,
> Kai
>
> Index: eh_personality.cc
> ===================================================================
> --- eh_personality.cc (Revision 193669)
> +++ eh_personality.cc (Arbeitskopie)
> @@ -332,13 +332,13 @@
> #ifdef _GLIBCXX_SJLJ_EXCEPTIONS
> #define PERSONALITY_FUNCTION __gxx_personality_sj0
> #define __builtin_eh_return_data_regno(x) x
> -#elif defined(__SEH__)
> +#elif defined(__SEH__) && !defined (_GLIBCXX_SJLJ_EXCEPTIONS)
> #define PERSONALITY_FUNCTION __gxx_personality_imp
> #else
> #define PERSONALITY_FUNCTION __gxx_personality_v0
> #endif
>
> -#ifdef __SEH__
> +#if defined (__SEH__) && !defined (_GLIBCXX_SJLJ_EXCEPTIONS)
> static
> #else
> extern "C"
> @@ -785,7 +785,7 @@
> }
> #endif
>
> -#ifdef __SEH__
> +#if defined (__SEH__) && !defined (_GLIBCXX_SJLJ_EXCEPTIONS)
> extern "C"
> EXCEPTION_DISPOSITION
> __gxx_personality_seh0 (PEXCEPTION_RECORD ms_exc, void *this_frame,
--
| (\_/) This is Bunny. Copy and paste
| (='.'=) Bunny into your signature to help
| (")_(") him gain world domination
next prev parent reply other threads:[~2012-11-28 18:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-25 15:42 Kai Tietz
2012-11-28 18:02 ` Kai Tietz [this message]
2012-11-28 18:54 ` Paolo Carlini
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='CAEwic4aPP130S1vTrqTUJTsB0T=zPD0-nnSm4obyVKTsSi_XpQ@mail.gmail.com' \
--to=ktietz70@googlemail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.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).