public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/97490] [10/11 Regression] false-positive -Wstringop-overflow= with address sanitizer since r10-5451-gef29b12cfbb4979a Date: Mon, 19 Oct 2020 12:07:34 +0000 [thread overview] Message-ID: <bug-97490-4-kGEohPUAF6@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97490-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97490 Martin Liška <marxin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2020-10-19 Summary|[10/11 Regression] |[10/11 Regression] |false-positive |false-positive |-Wstringop-overflow= with |-Wstringop-overflow= with |address sanitizer |address sanitizer since | |r10-5451-gef29b12cfbb4979a Ever confirmed|0 |1 Known to fail| |10.2.0, 11.0 Status|UNCONFIRMED |NEW Known to work| |9.3.0 --- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> --- Confirmed, started with Martin's commit.
next prev parent reply other threads:[~2020-10-19 12:07 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-19 11:15 [Bug sanitizer/97490] New: [10/11 Regression] false-positive -Wstringop-overflow= with address sanitizer arnd at linaro dot org 2020-10-19 12:05 ` [Bug sanitizer/97490] " rguenth at gcc dot gnu.org 2020-10-19 12:07 ` marxin at gcc dot gnu.org [this message] 2021-02-26 12:13 ` [Bug sanitizer/97490] [10/11 Regression] false-positive -Wstringop-overflow= with address sanitizer since r10-5451-gef29b12cfbb4979a rguenth at gcc dot gnu.org 2021-04-08 12:02 ` rguenth at gcc dot gnu.org 2022-06-28 10:42 ` [Bug sanitizer/97490] [10/11/12/13 " jakub at gcc dot gnu.org 2023-07-07 10:38 ` [Bug sanitizer/97490] [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-97490-4-kGEohPUAF6@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).