From: Jason Merrill <jason@redhat.com>
To: gcc@gcc.gnu.org
Cc: Dave Korn <dave.korn.cygwin@googlemail.com>,
SD <stardust496@gmail.com>,
"gcc@gcc.gnu.org >> GCC" <gcc@gcc.gnu.org>
Subject: Re: Exception handling information
Date: Tue, 25 Aug 2009 20:11:00 -0000 [thread overview]
Message-ID: <4A93FE5F.2090102@redhat.com> (raw)
Message-ID: <20090825201100.wJfcFkUI9rU5WGZ02vW374f_ah7_nA5NXyHK8Gq2WS8@z> (raw)
In-Reply-To: <m3zl9t6dnq.fsf@google.com>
On 08/20/2009 11:36 PM, Ian Lance Taylor wrote:
> Ironically, -freorder-blocks-and-partition, which seems tailor-made to
> fix this, is disabled when exception handling is used.
This is no longer true:
2009-08-07 Jakub Jelinek <jakub@redhat.com>
...
* opts.c: Include except.h.
(decode_options): Allow -freorder-blocks-and-partition with
exceptions, unless SJLJ or TARGET_UNWIND_INFO.
Jason
next prev parent reply other threads:[~2009-08-25 15:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-21 6:38 SD
2009-08-21 6:45 ` Dave Korn
2009-08-21 7:48 ` Ian Lance Taylor
2009-08-25 18:43 ` Jason Merrill [this message]
2009-08-25 20:11 ` Jason Merrill
2009-08-25 22:25 ` Ian Lance Taylor
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=4A93FE5F.2090102@redhat.com \
--to=jason@redhat.com \
--cc=dave.korn.cygwin@googlemail.com \
--cc=gcc@gcc.gnu.org \
--cc=stardust496@gmail.com \
/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).