public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/102276] New: -ftrivial-auto-var-init fails to initialize a variable, causes a spurious warning Date: Fri, 10 Sep 2021 14:17:52 +0000 [thread overview] Message-ID: <bug-102276-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102276 Bug ID: 102276 Summary: -ftrivial-auto-var-init fails to initialize a variable, causes a spurious warning Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: amonakov at gcc dot gnu.org Target Milestone: --- int g(int *); int f1() { switch (0) { int x; default: return g(&x); } } int f2() { goto L; { int x; L: return g(&x); } } Compiling with -O2 -ftrivial-auto-var-init=pattern causes spurious warning: statement will never be executed [-Wswitch-unreachable] 5 | int x; | ^ In both f1 and f2, resulting assembly does not in fact initialize 'x': f1: subq $24, %rsp leaq 12(%rsp), %rdi call g addq $24, %rsp ret f2: subq $24, %rsp leaq 12(%rsp), %rdi call g addq $24, %rsp ret
next reply other threads:[~2021-09-10 14:17 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-10 14:17 amonakov at gcc dot gnu.org [this message] 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
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@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).