From: Paolo Bonzini <bonzini@gnu.org>
To: gcc-patches@gcc.gnu.org
Subject: Re: RFA: New pass to delete unexecutable paths in the CFG
Date: Tue, 08 Nov 2011 11:50:00 -0000 [thread overview]
Message-ID: <j9b35s$vnb$1@dough.gmane.org> (raw)
In-Reply-To: <4EB8296D.1030802@redhat.com>
On 11/07/2011 07:54 PM, Jeff Law wrote:
> But we're still stuck with the conditional leading to the path with
> the __builtin_trap. That's what we want to avoid since those
> conditionals are executed at runtime.
Just to understand, what does this do with your optimization?
void f(void *p)
{
if (p)
{
puts("sell_soul_to_devil");
puts("post_reload_rewrite");
}
*p = 2;
}
...
f(NULL);
Does the program sell its soul to the devil before crashing?
Paolo
next prev parent reply other threads:[~2011-11-08 11:18 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 9:58 Jeff Law
2011-11-07 10:19 ` Jakub Jelinek
2011-11-07 10:21 ` Richard Guenther
2011-11-07 10:30 ` Richard Guenther
2011-11-07 19:20 ` Jeff Law
2011-11-07 16:14 ` Jeff Law
2011-11-07 16:30 ` Richard Guenther
2011-11-07 16:57 ` Kai Tietz
2011-11-07 19:03 ` Jeff Law
2011-11-08 11:50 ` Paolo Bonzini [this message]
2011-11-08 19:48 ` Jeff Law
2011-11-08 20:38 ` Paolo Bonzini
2011-11-08 20:59 ` Jeff Law
2011-11-09 8:37 ` Paolo Bonzini
2011-11-09 18:11 ` Jeff Law
2011-11-09 18:12 ` Jakub Jelinek
2011-11-09 22:45 ` Paolo Bonzini
2011-11-10 19:27 ` Jeff Law
2011-11-07 19:14 ` Jeff Law
2011-11-07 14:16 ` Tom Tromey
2011-11-07 15:54 ` Jeff Law
2011-11-07 15:54 ` Richard Guenther
2011-11-07 19:09 ` Jeff Law
2011-11-07 22:34 ` Richard Guenther
2011-11-08 20:02 ` Jeff Law
2011-11-09 9:50 ` Richard Guenther
2011-11-09 17:43 ` Jeff Law
2011-11-07 15:55 ` Tom Tromey
2011-11-07 17:01 ` Paolo Bonzini
2011-11-15 7:52 ` RFA: disable -fdelete-null-pointer-checks for Java Jeff Law
2011-11-07 19:05 ` RFA: New pass to delete unexecutable paths in the CFG Jeff Law
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='j9b35s$vnb$1@dough.gmane.org' \
--to=bonzini@gnu.org \
--cc=gcc-patches@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).