From: Jeff Prothero <jprother@altera.com>
To: <gcc@gcc.gnu.org>
Subject: Re: Obscure crashes due to gcc 4.9 -O2 => -fisolate-erroneous-paths-dereference
Date: Fri, 20 Feb 2015 01:04:00 -0000 [thread overview]
Message-ID: <pdf3861tmux.fsf@sj-interactive3.altera.com> (raw)
(Thanks to everyone for the helpful feedback!)
Daniel Gutson wrote:
> what about then two warnings (disabled by default), one intended to
> tell the user each time the compiler removes a conditional
> (-fdelete-null-pointer-checks)
> and another intended to tell the user each time the compiler adds a
> trap due to dereference an address 0?
>
> E.g.
> -Wnull-pointer-check-deleted
> -Wnull-dereference-considered-erroneous
I very much like the idea of such warnings.
I'm not clear why one would not warn by default when detecting
non-standards-conformant code and producing code guaranteed not
to do what the programmer intended. But presumably most sane
engineers these days compile with -Wall. :-)
-Jeff
next reply other threads:[~2015-02-20 1:04 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 1:04 Jeff Prothero [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-02-27 22:13 Manuel López-Ibáñez
2015-03-03 8:41 ` Chris Johns
2015-02-18 19:24 Jeff Prothero
2015-02-18 19:29 ` Jakub Jelinek
2015-02-19 20:56 ` Sandra Loosemore
2015-02-19 21:16 ` Daniel Gutson
2015-02-19 22:10 ` Jakub Jelinek
2015-02-19 22:26 ` Sandra Loosemore
2015-02-19 21:23 ` Joel Sherrill
2015-02-19 21:56 ` Chris Johns
2015-02-20 17:30 ` Jeff Law
2015-02-26 16:23 ` David Malcolm
2015-02-20 11:06 ` Florian Weimer
2015-02-20 11:43 ` Jonathan Wakely
2015-02-20 12:05 ` Florian Weimer
2015-02-20 17:01 ` Jeff Law
2015-02-20 17:09 ` Florian Weimer
2015-02-20 17:32 ` Jeff Law
2015-02-20 18:01 ` Paul_Koning
2015-02-20 12:11 ` Jakub Jelinek
2015-02-20 17:03 ` Jeff Law
2015-03-03 19:57 ` Martin Sebor
2015-03-03 23:38 ` Jeff Law
2015-03-04 12:36 ` Richard Biener
2015-02-20 12:13 ` Andrew Haley
2015-02-20 17:03 ` Jeff Law
2015-02-18 19:30 ` Andrew Pinski
2015-02-20 9:30 ` Andrew Haley
2015-02-20 11:45 ` Florian Weimer
2015-02-20 17:01 ` Jeff Law
2015-02-20 18:07 ` Paul_Koning
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=pdf3861tmux.fsf@sj-interactive3.altera.com \
--to=jprother@altera.com \
--cc=gcc@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).