public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "law at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/91470] [10/11/12 Regression] bogus uninitialized warning in trans-intrinsic.c Date: Sun, 20 Nov 2022 04:35:09 +0000 [thread overview] Message-ID: <bug-91470-4-6ziSDBfXWq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-91470-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91470 Jeffrey A. Law <law at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[10/11/12/13 Regression] |[10/11/12 Regression] bogus |bogus uninitialized warning |uninitialized warning in |in trans-intrinsic.c |trans-intrinsic.c --- Comment #9 from Jeffrey A. Law <law at gcc dot gnu.org> --- Seems to be fixed on the trunk so removing 13 regression marker. Leaving others, though I doubt backporting the changes to fix this is likely to happen.
next prev parent reply other threads:[~2022-11-20 4:35 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-91470-4@http.gcc.gnu.org/bugzilla/> 2021-01-14 8:18 ` [Bug tree-optimization/91470] [10/11 " rguenth at gcc dot gnu.org 2021-04-16 0:06 ` msebor at gcc dot gnu.org 2021-04-27 11:38 ` [Bug tree-optimization/91470] [10/11/12 " jakub at gcc dot gnu.org 2021-05-04 12:31 ` rguenth at gcc dot gnu.org 2021-07-28 7:04 ` rguenth at gcc dot gnu.org 2022-04-21 7:47 ` rguenth at gcc dot gnu.org 2022-11-20 4:35 ` law at gcc dot gnu.org [this message] 2022-11-21 6:48 ` rguenth at gcc dot gnu.org 2022-12-27 14:48 ` marxin at gcc dot gnu.org 2023-01-09 10:04 ` rguenth at gcc dot gnu.org 2023-05-29 10:02 ` 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-91470-4-6ziSDBfXWq@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).