public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/95589] missing warning initializing a reference with a dereferenced null
Date: Mon, 08 Jun 2020 19:29:50 +0000 [thread overview]
Message-ID: <bug-95589-4-BFNmMIv38F@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95589-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95589
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=84316
Blocks| |86172
Keywords| |diagnostic
--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
I was about to classify this as an enhancement but after reading the
description of -Wnull-dereference in the manual ("compiler detects paths that
trigger erroneous or undefined behavior due to dereferencing a null pointer")
I'm inclined to view it as a bug. The code is clearly in error, GCC just
doesn't detect it (even though the "doesn't detect it" part could be used to
argue the warning works strictly as documented).
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86172
[Bug 86172] [meta-bug] issues with -Wnull-dereference
next prev parent reply other threads:[~2020-06-08 19:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 19:25 [Bug c++/95589] New: " msebor at gcc dot gnu.org
2020-06-08 19:29 ` msebor at gcc dot gnu.org [this message]
2021-08-13 8:13 ` [Bug c++/95589] " egallager 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-95589-4-BFNmMIv38F@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).