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/95855] A missing ifcvt optimization to generate fcsel
Date: Tue, 30 Jun 2020 13:54:31 +0000 [thread overview]
Message-ID: <bug-95855-4-RIUXRrfNBV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95855-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95855
--- Comment #1 from CVS 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:33d114f570b4a3583421c700396fd5945acebc28
commit r11-1731-g33d114f570b4a3583421c700396fd5945acebc28
Author: Yang Yang <yangyang305@huawei.com>
Date: Tue Jun 30 18:04:31 2020 +0800
tree-optimization/95855 - Add checks to avoid spoiling if-conversion if
Add some checks in pass_splits_paths, so that pass_split_paths can
recognize the missed if-conversion opportunity and do not duplicate the
corresponding block.
2020-06-30 Yang Yang <yangyang305@huawei.com>
gcc/ChangeLog:
PR tree-optimization/95855
* gimple-ssa-split-paths.c (is_feasible_trace): Add extra
checks to recognize a missed if-conversion opportunity when
judging whether to duplicate a block.
gcc/testsuite/ChangeLog
PR tree-optimization/95855
* gcc.dg/tree-ssa/split-path-12.c: New testcase.
next prev parent reply other threads:[~2020-06-30 13:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 2:48 [Bug tree-optimization/95855] New: " yangyang305 at huawei dot com
2020-06-30 13:54 ` cvs-commit at gcc dot gnu.org [this message]
2021-05-30 23:07 ` [Bug tree-optimization/95855] " 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-95855-4-RIUXRrfNBV@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: link
Be 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).