public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/89976] [12/13/14/15 Regression] missing -Wuninitialized for struct member due to sra and TREE_NO_WARNING Date: Fri, 19 Jul 2024 13:04:35 +0000 [thread overview] Message-ID: <bug-89976-4-oD0bQGpSK3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-89976-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89976 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|11.5 |12.5 --- Comment #11 from Richard Biener <rguenth at gcc dot gnu.org> --- GCC 11 branch is being closed.
prev parent reply other threads:[~2024-07-19 13:04 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-89976-4@http.gcc.gnu.org/bugzilla/> 2020-06-23 21:03 ` [Bug c++/89976] missing uninitialized warning for uninitialized struct member (VOPs) msebor at gcc dot gnu.org 2021-04-01 23:10 ` msebor at gcc dot gnu.org 2021-04-16 21:30 ` [Bug tree-optimization/89976] [9/10/11 Regression] missing -Wuninitialized for struct member due to sra and TREE_NO_WARNING msebor at gcc dot gnu.org 2021-04-19 7:20 ` rguenth at gcc dot gnu.org 2021-06-01 8:13 ` [Bug tree-optimization/89976] [9/10/11/12 " rguenth at gcc dot gnu.org 2021-06-26 15:17 ` egallager at gcc dot gnu.org 2021-06-28 20:06 ` msebor at gcc dot gnu.org 2022-05-27 9:40 ` [Bug tree-optimization/89976] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:37 ` jakub at gcc dot gnu.org 2023-07-07 10:35 ` [Bug tree-optimization/89976] [11/12/13/14 " rguenth at gcc dot gnu.org 2024-07-19 13:04 ` rguenth at gcc dot gnu.org [this message]
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-89976-4-oD0bQGpSK3@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).