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/113796] [14 Regression] ifcvt does not remove range info before folding: Runtime mismatch at -O2 Date: Wed, 07 Feb 2024 12:06:05 +0000 [thread overview] Message-ID: <bug-113796-4-BUzodiCzeo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113796-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113796 --- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> --- We're removing flow-sensitive info in combine_blocks, but after inserting and folding stmts comprising the PHI replacements. There's possibly latent issues when building up the predicates themselves since that uses maybe_fold_or_comparisons without the workaround added for if-combine. I have a patch resetting flow-sensitive info earlier (and also covering PHIs).
next prev parent reply other threads:[~2024-02-07 12:06 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-07 6:14 [Bug target/113796] New: [14] RISC-V rv64gcv vector: " patrick at rivosinc dot com 2024-02-07 6:33 ` [Bug tree-optimization/113796] [14 Regression] " pinskia at gcc dot gnu.org 2024-02-07 6:35 ` pinskia at gcc dot gnu.org 2024-02-07 6:36 ` pinskia at gcc dot gnu.org 2024-02-07 6:48 ` pinskia at gcc dot gnu.org 2024-02-07 6:56 ` [Bug tree-optimization/113796] [14 Regression] ifcvt does not remove range info before folding: " pinskia at gcc dot gnu.org 2024-02-07 8:53 ` rguenth at gcc dot gnu.org 2024-02-07 12:06 ` rguenth at gcc dot gnu.org [this message] 2024-02-07 14:50 ` cvs-commit at gcc dot gnu.org 2024-02-07 14:50 ` 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-113796-4-BUzodiCzeo@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).