public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/115629] Inefficient if-convert of masked conditionals Date: Wed, 26 Jun 2024 16:53:34 +0000 [thread overview] Message-ID: <bug-115629-4-BuFfHLgBJn@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115629-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115629 --- Comment #2 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:629257bcb81434117f1e9c68479032563176dc0c commit r15-1662-g629257bcb81434117f1e9c68479032563176dc0c Author: Richard Biener <rguenther@suse.de> Date: Tue Jun 25 14:04:31 2024 +0200 tree-optimization/115629 - missed tail merging The following fixes a missed tail-merging observed for the testcase in PR115629. The issue is that when deps_ok_for_redirect doesn't compute both would be valid prevailing blocks it rejects the merge. The following instead makes sure to record the working block as prevailing. Also stmt comparison fails for indirect references and is not handling memory references thoroughly, failing to unify array indices and pointers indirected. The following attempts to fix this. PR tree-optimization/115629 * tree-ssa-tail-merge.cc (gimple_equal_p): Handle memory references better. (deps_ok_for_redirect): Handle the case not both blocks are considered a valid prevailing block. * gcc.dg/tree-ssa/tail-merge-1.c: New testcase.
next prev parent reply other threads:[~2024-06-26 16:53 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-25 5:44 [Bug tree-optimization/115629] New: " tnfchris at gcc dot gnu.org 2024-06-25 5:47 ` [Bug tree-optimization/115629] " pinskia at gcc dot gnu.org 2024-06-25 9:41 ` rguenth at gcc dot gnu.org 2024-06-26 16:53 ` cvs-commit at gcc dot gnu.org [this message] 2024-06-26 16:55 ` rguenth at gcc dot gnu.org 2024-07-01 10:10 ` tnfchris at gcc dot gnu.org 2024-07-01 12:27 ` rguenther at suse dot de 2024-07-01 19:33 ` tnfchris at gcc dot gnu.org 2024-07-02 7:03 ` rguenth at gcc dot gnu.org 2024-07-02 19:33 ` rsandifo 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-115629-4-BuFfHLgBJn@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).