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 tree-optimization/85741] [meta-bug] bogus/missing -Wformat-overflow
Date: Tue, 01 Dec 2020 20:58:32 +0000 [thread overview]
Message-ID: <bug-85741-4-xDqv40wk69@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-85741-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85741
Bug 85741 depends on bug 97373, which changed state.
Bug 97373 Summary: missing warning on sprintf into allocated destination
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97373
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
next prev parent reply other threads:[~2020-12-01 20:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-85741-4@http.gcc.gnu.org/bugzilla/>
2020-05-01 18:05 ` msebor at gcc dot gnu.org
2020-05-01 19:10 ` msebor at gcc dot gnu.org
2020-12-01 20:58 ` msebor at gcc dot gnu.org [this message]
2021-05-05 17:09 ` msebor at gcc dot gnu.org
2022-01-04 21:31 ` msebor at gcc dot gnu.org
2022-01-14 16:20 ` msebor at gcc dot gnu.org
2022-02-03 20:37 ` msebor at gcc dot gnu.org
2022-03-17 20:19 ` msebor at gcc dot gnu.org
2022-12-14 2:28 ` pinskia at gcc dot gnu.org
2023-01-24 21:16 ` pinskia at gcc dot gnu.org
2023-06-21 4:28 ` pinskia at gcc dot gnu.org
2023-06-21 4:33 ` pinskia at gcc dot gnu.org
2023-06-21 4:45 ` pinskia at gcc dot gnu.org
2023-07-07 9:21 ` rguenth at gcc dot gnu.org
2023-10-25 3:35 ` pinskia 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-85741-4-xDqv40wk69@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).