public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "qinzhao at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/102276] -ftrivial-auto-var-init fails to initialize a variable, causes a spurious warning Date: Wed, 02 Mar 2022 16:56:30 +0000 [thread overview] Message-ID: <bug-102276-4-bNgZSSOr0G@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102276-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102276 qinzhao at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #16 from qinzhao at gcc dot gnu.org --- Fixed in gcc12
prev parent reply other threads:[~2022-03-02 16:56 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-10 14:17 [Bug middle-end/102276] New: " amonakov at gcc dot gnu.org 2021-09-13 10:14 ` [Bug middle-end/102276] " rguenth at gcc dot gnu.org 2021-09-13 17:50 ` amonakov at gcc dot gnu.org 2021-09-14 17:55 ` kees at outflux dot net 2022-02-12 18:14 ` kees at outflux dot net 2022-02-12 20:22 ` pinskia at gcc dot gnu.org 2022-02-14 7:26 ` rguenth at gcc dot gnu.org 2022-02-14 16:08 ` jakub at gcc dot gnu.org 2022-02-14 17:02 ` qinzhao at gcc dot gnu.org 2022-02-14 23:21 ` qinzhao at gcc dot gnu.org 2022-02-15 8:16 ` rguenther at suse dot de 2022-02-15 16:02 ` qinzhao at gcc dot gnu.org 2022-02-15 19:55 ` qinzhao at gcc dot gnu.org 2022-02-17 7:22 ` rguenther at suse dot de 2022-02-17 19:57 ` qinzhao at gcc dot gnu.org 2022-03-02 16:55 ` cvs-commit at gcc dot gnu.org 2022-03-02 16:56 ` qinzhao 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-102276-4-bNgZSSOr0G@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).