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 middle-end/95507] [meta-bug] bogus/missing -Wnonnull
Date: Wed, 03 Jun 2020 16:48:22 +0000	[thread overview]
Message-ID: <bug-95507-4-O3KSWuMmNr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95507-4@http.gcc.gnu.org/bugzilla/>

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

Martin Sebor <msebor at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2020-06-03
     Ever confirmed|0                           |1
   Target Milestone|---                         |3.3
             Status|UNCONFIRMED                 |NEW

--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
-Wnonnull was introduced in r53790 which according to the manual was in the GCC
3.3 time frame.

  reply	other threads:[~2020-06-03 16:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-03 16:40 [Bug middle-end/95507] New: " msebor at gcc dot gnu.org
2020-06-03 16:48 ` msebor at gcc dot gnu.org [this message]
2020-06-03 20:14 ` [Bug middle-end/95507] " msebor at gcc dot gnu.org
2020-07-06 21:26 ` msebor at gcc dot gnu.org
2020-07-25 20:25 ` msebor at gcc dot gnu.org
2020-07-31 16:36 ` msebor at gcc dot gnu.org
2021-01-25 19:44 ` msebor at gcc dot gnu.org
2021-03-02 18:18 ` msebor at gcc dot gnu.org
2021-06-17 20:10 ` msebor at gcc dot gnu.org
2022-01-08 10:46 ` pinskia at gcc dot gnu.org
2023-02-02 22:39 ` pinskia at gcc dot gnu.org
2023-11-11  9:41 ` uecker 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-95507-4-O3KSWuMmNr@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).