public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/22568] Should use cmov in some stituations
Date: Mon, 24 May 2021 06:13:41 +0000	[thread overview]
Message-ID: <bug-22568-4-PtFNBzlBvQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-22568-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=22568

--- Comment #16 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #15)
> The expr.c patch yes.  The tree-ssa-phiopt.c patch, no.  Tree-ssa-phiopt.c
> needs more code rework because of the new infrastructures so I have not
> gotten around to improving the patch yet; been busy with other stuff.

The patch for PR 25290 includes the most of the infrastructure to implement
cmov at the gimple level (See match_simplify_replacement and late_p argument)
but is not enabled because I think it might require a cost model.

  parent reply	other threads:[~2021-05-24  6:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-22568-4@http.gcc.gnu.org/bugzilla/>
2012-02-08 21:01 ` pinskia at gcc dot gnu.org
2021-05-24  6:13 ` pinskia at gcc dot gnu.org [this message]
     [not found] <bug-22568-11024@http.gcc.gnu.org/bugzilla/>
2006-01-15  3:14 ` pinskia at gcc dot gnu dot org
2006-01-15  4:05 ` pinskia at gcc dot gnu dot org
2006-01-15 19:11 ` rguenth at gcc dot gnu dot org
2005-07-20 14:21 [Bug c++/22568] New: " arndt at jjj dot de
2005-07-20 15:14 ` [Bug rtl-optimization/22568] " pinskia at gcc dot gnu dot org
2005-08-31  9:42 ` rguenth at gcc dot gnu dot org
2005-09-01 12:38 ` rguenth at gcc dot gnu dot org
2005-09-02  9:47 ` bonzini at gcc dot gnu dot org
2005-09-02  9:54 ` rguenth at gcc dot gnu dot 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-22568-4-PtFNBzlBvQ@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).