public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kretz at kde dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/98834] New: Code path incorrectly determined to be unreachable Date: Tue, 26 Jan 2021 08:28:02 +0000 [thread overview] Message-ID: <bug-98834-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98834 Bug ID: 98834 Summary: Code path incorrectly determined to be unreachable Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: kretz at kde dot org Target Milestone: --- Target: x86_64-pc-linux-gnu Created attachment 50054 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50054&action=edit test case The attached testcase compiles to a main function without return statement, as if the compiler determines the code path is unreachable. Compile with -O2. If you compile with -O2 -fno-tree-vrp, the return statement is emitted.
next reply other threads:[~2021-01-26 8:28 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-26 8:28 kretz at kde dot org [this message] 2021-01-26 9:18 ` [Bug ipa/98834] [10/11 Regression] " rguenth at gcc dot gnu.org 2021-01-26 9:20 ` kretz at kde dot org 2021-01-26 9:29 ` kretz at kde dot org 2021-01-26 9:47 ` jakub at gcc dot gnu.org 2021-01-26 10:09 ` rguenther at suse dot de 2021-03-08 18:10 ` jamborm at gcc dot gnu.org 2021-03-15 12:40 ` rguenth at gcc dot gnu.org 2021-03-15 15:00 ` cvs-commit at gcc dot gnu.org 2021-03-15 15:02 ` rguenth at gcc dot gnu.org 2021-03-16 9:29 ` marxin at gcc dot gnu.org 2021-03-24 13:12 ` [Bug ipa/98834] [10 " rguenth at gcc dot gnu.org 2021-03-24 14:26 ` cvs-commit at gcc dot gnu.org 2021-03-24 14:27 ` 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-98834-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).