public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/110170] Sub-optimal conditional jumps in conditional-swap with floating point
Date: Fri, 09 Jun 2023 06:40:55 +0000	[thread overview]
Message-ID: <bug-110170-4-8ee2KCnLsU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110170-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Hongtao.liu <crazylht at gmail dot com> ---
(In reply to Hongtao.liu from comment #5)
> (In reply to Antony Polukhin from comment #2)
> > -fno-trapping-math had no effect
> > 
> > Some tests with nans seem to produce the same results for both code
> > snippets: https://godbolt.org/z/GaKM3EhMq
> 
> What about infinity, I notice
> With -ffinite-math-only -funsafe-math-optimizations, gcc now can generate 
> 
> __cond_swap(double*, double*):
>         movsd   (%rdi), %xmm0
>         movsd   (%rsi), %xmm1
>         movapd  %xmm0, %xmm2
>         minsd   %xmm1, %xmm0
>         maxsd   %xmm1, %xmm2
>         movsd   %xmm2, (%rsi)
>         movsd   %xmm0, (%rdi)
>         ret

Assume -funsafe-math-optimizations is not needed?

  parent reply	other threads:[~2023-06-09  6:40 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-08 11:31 [Bug tree-optimization/110170] New: " antoshkka at gmail dot com
2023-06-08 11:34 ` [Bug tree-optimization/110170] " pinskia at gcc dot gnu.org
2023-06-08 11:57 ` [Bug target/110170] " antoshkka at gmail dot com
2023-06-08 13:32 ` pinskia at gcc dot gnu.org
2023-06-08 19:40 ` pinskia at gcc dot gnu.org
2023-06-09  5:38 ` crazylht at gmail dot com
2023-06-09  6:40 ` crazylht at gmail dot com [this message]
2023-06-09  7:01 ` crazylht at gmail dot com
2023-06-09  7:03 ` rguenth at gcc dot gnu.org
2023-06-12  2:17 ` crazylht at gmail dot com
2023-06-12  9:09 ` crazylht at gmail dot com
2023-07-04  5:46 ` crazylht at gmail dot com
2023-07-06  5:54 ` cvs-commit at gcc dot gnu.org
2023-07-10  1:06 ` cvs-commit at gcc dot gnu.org
2023-07-11  9:51 ` antoshkka at gmail dot com
2023-07-11 13:23 ` crazylht at gmail dot com
2023-07-11 13:57 ` cvs-commit at gcc dot gnu.org
2023-07-18 10:28 ` rguenth at gcc dot gnu.org
2023-07-18 10:33 ` crazylht at gmail dot com
2023-07-18 13:48 ` rguenth at gcc dot gnu.org
2023-07-21  8:18 ` rguenth at gcc dot gnu.org
2023-10-17  6:31 ` cvs-commit at gcc dot gnu.org
2023-10-17 11:14 ` cvs-commit at gcc dot gnu.org
2023-10-26  5:30 ` cvs-commit 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-110170-4-8ee2KCnLsU@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).