public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/101001] [9/10/11/12 Regression] wrong code at -O3 on x86_64-linux-gnu Date: Thu, 10 Jun 2021 07:26:08 +0000 [thread overview] Message-ID: <bug-101001-4-8EKJ56HMtn@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101001-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101001 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2021-06-10 Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Depends on| |100934 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- We end up with <bb 2> [count: 0]: b.1_18 ={v} b; b.1_5 ={v} b; ... b.1_1 ={v} b; __builtin_unreachable (); } sounds related to PR100934, "fixed" with -fdisable-tree-cunroll. Loop 1 iterates at most 15 times. Loop 1 likely iterates at most 15 times. -fdisable-tree-thread2 "fixes" it as well. Likely a duplicate. Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100934 [Bug 100934] [9/10/11/12 Regression] wrong code at -O3 during unrolling since r9-6299
next prev parent reply other threads:[~2021-06-10 7:26 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-09 19:37 [Bug tree-optimization/101001] New: " qrzhang at gatech dot edu 2021-06-10 6:50 ` [Bug tree-optimization/101001] [9/10/11/12 Regression] " rguenth at gcc dot gnu.org 2021-06-10 7:26 ` rguenth at gcc dot gnu.org [this message] 2021-06-14 9:43 ` jakub at gcc dot gnu.org 2021-10-13 10:10 ` rguenth at gcc dot gnu.org 2021-11-09 7:57 ` pinskia 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-101001-4-8EKJ56HMtn@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).