From: Matt Breedlove <breedlove.matt@gmail.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: Eric Botcazou <ebotcazou@adacore.com>,
gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org,
java-patches@gcc.gnu.org
Subject: Re: [patch] Clean up detection of SJLJ exceptions in target libraries
Date: Wed, 13 May 2015 12:11:00 -0000 [thread overview]
Message-ID: <CAD8UrCFf863DFTQZh13Aa4qy=jL_hy-uC6Do0cP8+1GwyBC98g@mail.gmail.com> (raw)
In-Reply-To: <20150513103655.GC30202@redhat.com>
This patch fixes an issue preventing mingw-w64 i686 dwarf2-eh
bootstrapping described at:
http://sourceforge.net/p/mingw-w64/mailman/message/34101954/
I'm assuming this has more to do with switching away from the current
sjlj configuration method since configuring gcc with
"--disable-sjlj-exceptions --with-dwarf2" still suffers the same
issues. Building with simply "--with-dwarf2" instead, however, now
works fine. I'm not sure whether or not a bug has been created for it
and if one needs to be.
Much appreciated,
Matt
On Wed, May 13, 2015 at 6:36 AM, Jonathan Wakely <jwakely@redhat.com> wrote:
> On 12/05/15 18:42 +0200, Eric Botcazou wrote:
>>
>> libstdc++-v3/
>> * acinclude.m4 (GLIBCXX_ENABLE_SJLJ_EXCEPTIONS): Delete.
>> * configure.ac: Remove GLIBCXX_ENABLE_SJLJ_EXCEPTIONS.
>> * config.h.in: Regenerate.
>> * configure: Likewise.
>> * libsupc++/eh_personality.cc: Replace _GLIBCXX_SJLJ_EXCEPTIONS by
>> __USING_SJLJ_EXCEPTIONS__.
>> * libsupc++/eh_throw.cc: Likewise.
>> * libsupc++/eh_ptr.cc: Likewise.
>> * doc/html/manual/appendix_porting.html: Remove
>> GLIBCXX_ENABLE_SJLJ_EXCEPTIONS
>> * doc/xml/manual/build_hacking.xml: Likewise.
>> * doc/html/manual/configure.html: Remove --enable-sjlj-exceptions.
>> * doc/xml/manual/configure.xml: Likewise.
>
>
> The libstdc++ parts are OK, thanks.
>
next prev parent reply other threads:[~2015-05-13 12:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-12 16:45 Eric Botcazou
2015-05-12 20:26 ` Jeff Law
2015-05-13 7:53 ` Eric Botcazou
2015-05-13 7:55 ` Andrew Pinski
2015-05-13 10:37 ` Jonathan Wakely
2015-05-13 12:11 ` Matt Breedlove [this message]
2015-05-13 16:11 ` Eric Botcazou
2015-05-13 16:26 ` Ian Lance Taylor
2015-05-13 17:53 ` Eric Botcazou
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='CAD8UrCFf863DFTQZh13Aa4qy=jL_hy-uC6Do0cP8+1GwyBC98g@mail.gmail.com' \
--to=breedlove.matt@gmail.com \
--cc=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=java-patches@gcc.gnu.org \
--cc=jwakely@redhat.com \
--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).