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/89697] [9/10/11 Regression] SRA prevents -Wuninitialized warning Date: Fri, 16 Apr 2021 21:29:07 +0000 [thread overview] Message-ID: <bug-89697-4-4IoQfoziKH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-89697-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89697 Martin Sebor <msebor at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Known to fail|9.2.0 |4.3.0, 4.8.4, 4.9.4, 5.5.0, | |6.4.0, 7.2.0, 8.3.0, 9.1.0 Summary|SRA prevents |[9/10/11 Regression] SRA |-Wuninitialized warning |prevents -Wuninitialized | |warning --- Comment #3 from Martin Sebor <msebor at gcc dot gnu.org> --- Bisection points to r128908 as the first revision when GCC failed to warn.
next prev parent reply other threads:[~2021-04-16 21:29 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-89697-4@http.gcc.gnu.org/bugzilla/> 2021-04-06 20:17 ` [Bug tree-optimization/89697] " msebor at gcc dot gnu.org 2021-04-16 21:29 ` msebor at gcc dot gnu.org [this message] 2021-04-19 7:20 ` [Bug tree-optimization/89697] [9/10/11 Regression] " rguenth at gcc dot gnu.org 2021-06-01 8:13 ` [Bug tree-optimization/89697] [9/10/11/12 " rguenth at gcc dot gnu.org 2022-03-22 13:02 ` rguenth at gcc dot gnu.org 2022-03-22 13:12 ` jakub at gcc dot gnu.org 2022-05-27 9:40 ` [Bug tree-optimization/89697] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:36 ` jakub at gcc dot gnu.org 2023-07-07 10:35 ` [Bug tree-optimization/89697] [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-89697-4-4IoQfoziKH@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).