public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: Tom Tromey <tromey@redhat.com>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: RFA: New pass to delete unexecutable paths in the CFG
Date: Mon, 07 Nov 2011 19:09:00 -0000	[thread overview]
Message-ID: <4EB82B89.7020208@redhat.com> (raw)
In-Reply-To: <CAFiYyc0_yrN7spUSS2RgM2TtjOQDbmXNTXyOwio+mxK89NRw9A@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 11/07/11 08:49, Richard Guenther wrote:

> 
> OTOH I'm not sure we want to change a possible trap (And thus 
> program abort) to a fallthru ...
I think this is the big question we need to answer; there's other
places were we rely upon ISO's standards to enable optimization.  But
this one just feels a little different...  Or maybe I'm shy after the
kernel security problem caused by relying on dereferenced pointer not
being null.

I could easily see not enabling the switch by default for a period of
time, or enabling the optimization by default along with some kind of
warning.

Jeff
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOuCuJAAoJEBRtltQi2kC7Q3cIAJRZGTaPlhQp3Y7fyx4A3rTJ
xmO45FkfkVba3NVqqCy2Ei95ezORhqzt2X31pzUuNZmyAXagnlizcY2uBNrgcRIl
+AltdDn3V+B19oABLrnVoxKjlb0yqHOKxikZcktFZuBB6zJBYOveWbWir5pMt2se
0K7pCXc6oe3MJfaYrPnZSkYEf5pcJw0ZKXxrK46HakWv5/oBi+kw5fo9aiEW0bhu
FQWxnfiNEsp4w+ac4PY/oQmcquI2AjeMrHiSKuZquC+r34SCYHMlSR9cED9WSy+7
RIlHygJYFcF9YwYEEbn61yyHfKbrIg6StizpkFVvu/oa2uDtqVFpFFBV0znO3aY=
=iF0s
-----END PGP SIGNATURE-----

  reply	other threads:[~2011-11-07 19:03 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
2011-11-07 15:54     ` Richard Guenther
2011-11-07 19:09       ` Jeff Law [this message]
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=4EB82B89.7020208@redhat.com \
    --to=law@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=richard.guenther@gmail.com \
    --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).