public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/105337] [12 Regression] wrong code at -Os and above on x86_64-linux-gnu Date: Thu, 21 Apr 2022 16:32:16 +0000 [thread overview] Message-ID: <bug-105337-4-6EGIcKeuTY@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105337-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105337 Marek Polacek <mpolacek at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P3 |P1 Status|UNCONFIRMED |NEW Target Milestone|--- |12.0 CC| |aoliva at gcc dot gnu.org, | |mpolacek at gcc dot gnu.org Ever confirmed|0 |1 Keywords| |wrong-code Last reconfirmed| |2022-04-21 Summary|wrong code at -Os and above |[12 Regression] wrong code |on x86_64-linux-gnu |at -Os and above on | |x86_64-linux-gnu --- Comment #2 from Marek Polacek <mpolacek at gcc dot gnu.org> --- Confirmed. Started with r12-397-gda9e6e63d1ae22, in particular this hunk: --- a/gcc/passes.def +++ b/gcc/passes.def @@ -336,8 +336,9 @@ along with GCC; see the file COPYING3. If not see NEXT_PASS (pass_thread_jumps); NEXT_PASS (pass_vrp, false /* warn_array_bounds_p */); /* Threading can leave many const/copy propagations in the IL. - Clean them up. */ - NEXT_PASS (pass_copy_prop); + Clean them up. Instead of just copy_prop, we use ccp to + compute alignment and nonzero bits. */ + NEXT_PASS (pass_ccp, true /* nonzero_p */); NEXT_PASS (pass_warn_restrict); NEXT_PASS (pass_dse); NEXT_PASS (pass_cd_dce, true /* update_address_taken_p */);
next prev parent reply other threads:[~2022-04-21 16:32 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-21 16:16 [Bug tree-optimization/105337] New: " zhendong.su at inf dot ethz.ch 2022-04-21 16:16 ` [Bug tree-optimization/105337] " zhendong.su at inf dot ethz.ch 2022-04-21 16:32 ` mpolacek at gcc dot gnu.org [this message] 2022-04-21 16:41 ` [Bug tree-optimization/105337] [12 Regression] " mpolacek at gcc dot gnu.org 2022-04-21 16:43 ` mpolacek at gcc dot gnu.org 2022-04-21 16:49 ` jakub at gcc dot gnu.org 2022-04-21 16:58 ` jakub at gcc dot gnu.org 2022-04-21 17:00 ` jakub at gcc dot gnu.org 2022-04-22 6:11 ` 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-105337-4-6EGIcKeuTY@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).