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/101917] [11 Regression] Spurious -Wstringop-overread with -flto when passing zero sized arrays Date: Wed, 10 Nov 2021 04:48:55 +0000 [thread overview] Message-ID: <bug-101917-4-dgOJ9mCBr2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101917-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101917 Martin Sebor <msebor at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Component|fortran |middle-end Summary|Spurious |[11 Regression] Spurious |-Wstringop-overread with |-Wstringop-overread with |-flto when passing zero |-flto when passing zero |sized arrays |sized arrays Ever confirmed|0 |1 Known to fail| |11.2.0 Blocks| |97048 Last reconfirmed| |2021-11-10 See Also| |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=103145 --- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> --- Confirmed with GCC 11, but fixed in GCC 12. Most likely a duplicate of pr103145. Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97048 [Bug 97048] [meta-bug] bogus/missing -Wstringop-overread warnings
next prev parent reply other threads:[~2021-11-10 4:48 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-15 8:40 [Bug fortran/101917] New: " rimvydas.jas at gmail dot com 2021-11-10 4:48 ` msebor at gcc dot gnu.org [this message] 2021-11-16 13:08 ` [Bug middle-end/101917] [11 Regression] " rguenth at gcc dot gnu.org 2022-04-21 7:50 ` rguenth at gcc dot gnu.org 2023-05-29 10:05 ` jakub 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-101917-4-dgOJ9mCBr2@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).