From: Richard Guenther <rguenther@suse.de>
To: Eric Botcazou <ebotcazou@adacore.com>
Cc: gcc-patches@gcc.gnu.org, "Joseph S. Myers" <joseph@codesourcery.com>
Subject: Re: [PATCH] Fix PR50999, serialize frontend specific flags (-fexceptions)
Date: Mon, 07 Nov 2011 14:11:00 -0000 [thread overview]
Message-ID: <alpine.LNX.2.00.1111071432570.4527@zhemvz.fhfr.qr> (raw)
In-Reply-To: <alpine.LNX.2.00.1111071341210.4527@zhemvz.fhfr.qr>
On Mon, 7 Nov 2011, Richard Guenther wrote:
> On Mon, 7 Nov 2011, Eric Botcazou wrote:
>
> > > This tries to find a way to prepend explicitly set command-line options
> > > by those implicitly set by the frontend (-fexceptions in this case).
> > > Unfortunately we don't seem to have a good way to extract this information
> > > easily, so for -fexceptions I hope all frontends set that during
> > > init_options_struct.
> >
> > That's wrong for Ada: it is set in gnat_init_gcc_eh and cannot be set earlier
> > because we support run time selection of the EH scheme.
Btw, I doubt the patch would break anything for Ada - it at most
adds -fexceptions, so if Ada doesn't set flag_exceptions in
init_options_struct then it is a no-op for Ada.
Richard.
next prev parent reply other threads:[~2011-11-07 13:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 12:40 Richard Guenther
2011-11-07 12:49 ` Iain Sandoe
2011-11-07 12:50 ` Richard Guenther
2011-11-07 12:51 ` Iain Sandoe
2011-11-07 13:15 ` Richard Guenther
2011-11-08 0:30 ` Joseph S. Myers
2011-11-08 14:51 ` Iain Sandoe
2011-11-08 14:53 ` Richard Guenther
2011-11-07 12:49 ` Eric Botcazou
2011-11-07 13:08 ` Richard Guenther
2011-11-07 14:11 ` Richard Guenther [this message]
2011-11-08 0:30 ` Joseph S. Myers
2011-11-08 0:27 ` Joseph S. Myers
2011-11-08 14:00 ` Richard Guenther
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=alpine.LNX.2.00.1111071432570.4527@zhemvz.fhfr.qr \
--to=rguenther@suse.de \
--cc=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.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).