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/90036] [8/9/10/11 Regression] false positive: directive argument is null [-Werror=format-overflow=] Date: Wed, 10 Feb 2021 22:34:26 +0000 [thread overview] Message-ID: <bug-90036-4-MlzvmhYtOl@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-90036-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90036 Martin Sebor <msebor at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|11.0 |12.0 Known to fail|9.0 |10.2.0, 11.0, 9.3.0 Last reconfirmed|2019-04-10 00:00:00 |2021-2-10 --- Comment #11 from Martin Sebor <msebor at gcc dot gnu.org> --- No progress in GCC 11 but hopefully in GCC 12.
next prev parent reply other threads:[~2021-02-10 22:34 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-90036-4@http.gcc.gnu.org/bugzilla/> 2020-05-01 18:00 ` msebor at gcc dot gnu.org 2021-02-10 22:34 ` msebor at gcc dot gnu.org [this message] 2022-05-06 8:30 ` [Bug c/90036] [9/10/11/12/13 " jakub at gcc dot gnu.org 2023-05-08 12:21 ` [Bug c/90036] [10/11/12/13/14 " rguenth 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-90036-4-MlzvmhYtOl@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: linkBe 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).