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 c/59424] Optimization issue on min/max
Date: Mon, 09 Dec 2013 14:49:00 -0000	[thread overview]
Message-ID: <bug-59424-4-6w6ea8nqel@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59424-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59424

--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Marek Polacek from comment #1)
> I can observe the same behavior with trunk.
> 
> For func2, we compute a < b ? a : b first and then call sqrtf on that, while
> for func3 we have return a < b ? ABS_EXPR <a> : ABS_EXPR <b>;.  Perhaps
> that's the reason why ifcvt doesn't optimize this using UNSPEC_IEEE_MIN.

Yep.  Obviously it cannot after that distribution of ABS_EXPR.


  parent reply	other threads:[~2013-12-09 14:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-09  6:01 [Bug c/59424] New: " jmvalin at jmvalin dot ca
2013-12-09 11:13 ` [Bug c/59424] " mpolacek at gcc dot gnu.org
2013-12-09 14:49 ` rguenth at gcc dot gnu.org [this message]
2013-12-09 17:05 ` jmvalin at jmvalin dot ca
2021-07-06  8:18 ` [Bug middle-end/59424] " pinskia at gcc dot gnu.org
2023-05-08  7:38 ` cvs-commit at gcc dot gnu.org
2023-05-08  7:41 ` 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-59424-4-6w6ea8nqel@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).