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/92815] [8/9/10 Regression] spurious -Wstringop-overflow writing into a flexible array of an extern struct Date: Mon, 18 May 2020 21:26:03 +0000 [thread overview] Message-ID: <bug-92815-4-8Yfm1Vjj9L@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-92815-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92815 Martin Sebor <msebor at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Known to work| |11.0 Summary|[8/9/10/11 Regression] |[8/9/10 Regression] |spurious |spurious |-Wstringop-overflow writing |-Wstringop-overflow writing |into a flexible array of an |into a flexible array of an |extern struct |extern struct --- Comment #7 from Martin Sebor <msebor at gcc dot gnu.org> --- Fixed on trunk for now.
next prev parent reply other threads:[~2020-05-18 21:26 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-92815-4@http.gcc.gnu.org/bugzilla/> 2020-04-22 21:38 ` msebor at gcc dot gnu.org 2020-05-18 21:25 ` [Bug middle-end/92815] [8/9/10/11 " cvs-commit at gcc dot gnu.org 2020-05-18 21:26 ` msebor at gcc dot gnu.org [this message] 2020-05-18 22:33 ` [Bug middle-end/92815] [8/9/10 " cvs-commit at gcc dot gnu.org 2020-05-25 15:44 ` asolokha at gmx dot com 2021-05-14 9:52 ` [Bug middle-end/92815] [9/10 " jakub at gcc dot gnu.org 2021-06-01 8:15 ` rguenth at gcc dot gnu.org 2022-05-27 9:41 ` [Bug middle-end/92815] [10 " rguenth at gcc dot gnu.org 2022-06-28 10:39 ` jakub at gcc dot gnu.org 2023-07-07 8:45 ` 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-92815-4-8Yfm1Vjj9L@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).