public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "R.E.Wolff at BitWizard dot nl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/96554] -Wall does not include -Wnull-dereference
Date: Mon, 10 Aug 2020 13:02:28 +0000	[thread overview]
Message-ID: <bug-96554-4-OvVbzHiqI8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96554-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96554

--- Comment #2 from Roger Wolff <R.E.Wolff at BitWizard dot nl> ---
In my case it promotes a function I didn't declare as <does not return> into
one that <does not return> and thereby it caused 80% of my code to become
"dead". It'd be nice to differentiate between the case where a simple
optimization removes a few lines of code due to an extra null-check not being
reachable due to the trap  on the null dereference and the case where big
unexpected things start happening. 

Maybe the promotion of a function from "does return" to "does not return" is
something you might warn about. This satisfies the "you can easily modify the
code to silence the warning".

  parent reply	other threads:[~2020-08-10 13:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-10 12:36 [Bug c/96554] New: " R.E.Wolff at BitWizard dot nl
2020-08-10 12:48 ` [Bug c/96554] " jakub at gcc dot gnu.org
2020-08-10 13:02 ` R.E.Wolff at BitWizard dot nl [this message]
2020-08-10 13:03 ` schwab@linux-m68k.org
2020-08-10 13:10 ` R.E.Wolff at BitWizard dot nl
2020-08-10 15:50 ` [Bug tree-optimization/96554] " msebor at gcc dot gnu.org
2020-08-10 18:56 ` rsandifo at gcc dot gnu.org

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=bug-96554-4-OvVbzHiqI8@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).