public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/65917] [6.0 regression] FAIL: gcc.dg/tree-ssa/20030922-2.c scan-tree-dump-times dom1 "if " 2 Date: Tue, 28 Apr 2015 16:24:00 -0000 [thread overview] Message-ID: <bug-65917-4-yNE5g7iQNT@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65917-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65917 --- Comment #4 from Jeffrey A. Law <law at redhat dot com> --- We'll probably need to XFAIL this for now. This is definitely a case where we were just getting lucky before and the new code to canonicalize the comparison arguments causes us not to get lucky. The single use heuristic doesn't help here, because both operands have multiple uses. I'd pondered walking up the use-def chains to guess which operand is more expensive to compute and use that as a heuristic as well, but in this case it'd do the opposite of what we want. I don't see other obvious heuristics that would resolve this issue. The "right" way to fix this would be to unify cprop and simplification -- ie, when we have a statement that references an SSA_NAME with one of these equivalences, we need to try both SSA_NAMEs and see if it simplifies. I've avoided doing that simply because it hasn't seemed worth the effort and compile-time cost.
next prev parent reply other threads:[~2015-04-28 16:24 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-04-28 13:55 [Bug tree-optimization/65917] New: " schwab@linux-m68k.org 2015-04-28 14:06 ` [Bug tree-optimization/65917] " rguenth at gcc dot gnu.org 2015-04-28 14:51 ` schwab@linux-m68k.org 2015-04-28 14:58 ` law at redhat dot com 2015-04-28 16:24 ` law at redhat dot com [this message] 2015-04-29 8:45 ` [Bug tree-optimization/65917] [6 Regression] " rguenth at gcc dot gnu.org 2015-04-29 8:51 ` rguenth at gcc dot gnu.org 2015-04-29 8:52 ` [Bug tree-optimization/65917] [6 Regression] XFAIL: " rguenth at gcc dot gnu.org 2023-03-24 7:35 ` 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-65917-4-yNE5g7iQNT@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).