public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/86172] [meta-bug] issues with -Wnull-dereference
Date: Fri, 13 Aug 2021 08:17:20 +0000 [thread overview]
Message-ID: <bug-86172-4-ffFElVryYm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-86172-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86172
--- Comment #7 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Segher Boessenkool from comment #6)
> Thanks for the information Eric.
>
> Will it help if the option is split into -Wnull-dereference and
> -Wmaybe-null-dereference (as suggested before)?
This discussion is now in bug 96554
next prev parent reply other threads:[~2021-08-13 8:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-86172-4@http.gcc.gnu.org/bugzilla/>
2021-04-15 23:05 ` msebor at gcc dot gnu.org
2021-08-13 8:17 ` egallager at gcc dot gnu.org [this message]
2023-07-07 8:49 ` rguenth at gcc dot gnu.org
2023-11-07 11:38 ` redi at gcc dot gnu.org
2024-05-13 11:11 ` redi 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-86172-4-ffFElVryYm@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).