From: Eric Botcazou <ebotcazou@adacore.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Jeff Law <law@redhat.com>, Richard Biener <rguenther@suse.de>,
gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Don't DCE const/pure calls that can throw if cfg can't be altered (PR rtl-optimization/88870)
Date: Thu, 17 Jan 2019 11:27:00 -0000 [thread overview]
Message-ID: <3843448.kfWJntclgd@polaris> (raw)
In-Reply-To: <20190116225104.GC30353@tucnak>
> AFAIK Ada and Go use -fnon-call-exceptions by default and heavily rely on
> it.
Right, the Ada compiler uses -fnon-call-exceptions -fdelete-dead-exceptions
and ACATS could not be passed with optimization enabled without the former.
Btw, there are a couple of improper direct uses of flag_non_call_exceptions in
the sources, may I change them to cfun->can_throw_non_call_exceptions?
gimple-ssa-isolate-paths.c: if (!flag_non_call_exceptions)
gimple-ssa-isolate-paths.c: if (!flag_non_call_exceptions
tree-ssa-alias.c: if (flag_non_call_exceptions && pi->pt.null)
--
Eric Botcazou
next prev parent reply other threads:[~2019-01-17 11:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 22:43 Jakub Jelinek
2019-01-16 22:48 ` Jeff Law
2019-01-16 22:51 ` Jakub Jelinek
2019-01-17 7:59 ` Arnaud Charlet
2019-01-17 11:27 ` Eric Botcazou [this message]
2019-01-17 11:33 ` Jakub Jelinek
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=3843448.kfWJntclgd@polaris \
--to=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=law@redhat.com \
--cc=rguenther@suse.de \
/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).