From: Jeff Law <law@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: RFA: New pass to delete unexecutable paths in the CFG
Date: Mon, 07 Nov 2011 15:54:00 -0000 [thread overview]
Message-ID: <4EB7FCAA.10100@redhat.com> (raw)
In-Reply-To: <m3sjm0nind.fsf@fleche.redhat.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 11/07/11 06:53, Tom Tromey wrote:
>>>>>> "Jeff" == Jeff Law <law@redhat.com> writes:
>
> Jeff> First, it's perfectly fine to have a NULL pointer dereference
> in a Jeff> program as long as that code is never executed. Once
> the code is Jeff> executed, we've entered the realm of undefined
> behavior.
>
> Jeff> Thus in a conforming program we can safely assume that a
> provable NULL Jeff> pointer dereference can never be executed at
> runtime. This implies Jeff> there is a path through the CFG that
> is unexecutable.
>
> IIUC, then this isn't true for Java. In Java the attempt to
> dereference NULL throws a NullPointerException, which can be
> caught, etc. It isn't undefined.
So, presumably there's no way to know we're throwing to
NullPointerException from the exception information attached to the
statement or BB? If not I could disable if the statement with the
memory op throws anywhere. It's not ideal, but conservatively correct.
jeff
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJOt/ypAAoJEBRtltQi2kC7uhIH/jpk2jx7mn7i/RVA9jqiR3BU
tz4KRL1+giqWj8B2gG+y6vn8tBOFrruymIP4ewRjO1Q6IIvlDr6dyWSIXAw/TQ8g
p0V7Cfk+cxOkMJ6m6T/qpHjdtJsfx9FYQF6JSHPpalzh7FxlSIVJ9vGejmNqjHHG
ZxqDZd8emz0e7C4KtrX5mkMSZDHXo2+vWulwf8lwCJBjDLLR0nylv5GFREIuSDDR
BEkosWYfgJfngjmiwiXu8re9kEBpdRlnzDh+416VkSKTwjqHvqnb1Ux3rlBKHR7U
/DAQVcFNYdjwHFmTjvc50NPgOMf1fMEw9wCaMtL1THJlRMwpyaR5R8Gc+PiQjLk=
=bdeT
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-11-07 15:44 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
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 [this message]
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=4EB7FCAA.10100@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=tromey@redhat.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).