public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/103605] [PowerPC] fmin/fmax should be inlined always with xsmindp/xsmaxdp
Date: Thu, 28 Apr 2022 03:22:14 +0000 [thread overview]
Message-ID: <bug-103605-4-wBC8QGNt6e@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103605-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103605
--- Comment #7 from Kewen Lin <linkw at gcc dot gnu.org> ---
(In reply to pc from comment #5)
> I modified the testcase from comment #3 to clear-before and check-after
> FE_INVALID exception bit for each operation:
> --
> $ /opt/gcc-nightly/trunk/bin/gcc -O2 -o xsmindp-test xsmindp-test.c
> xsmindp.c -lm && ./xsmindp-test a b
> (src1, src2): fmin:I b-in:I asm:I
> (+3.0, +3.0): +3.0;0 +3.0;0 +3.0;0
> (+3.0, NAN): +3.0;0 +nan;0 +3.0;0
> ( NAN, +3.0): +3.0;0 +3.0;0 +3.0;0
> ( NAN, NAN): +nan;0 +nan;0 +nan;0
> (+3.0, SNAN): +nan;1 +nan;1 +nan;1
> (SNAN, +3.0): +nan;1 +3.0;1 +nan;1
> (SNAN, SNAN): +nan;1 +nan;1 +nan;1
> $ /opt/gcc-nightly/trunk/bin/gcc -O2 -ffast-math -o xsmindp-test
> xsmindp-test.c xsmindp.c -lm && ./xsmindp-test a b
> (src1, src2): fmin:I b-in:I asm:I
> (+3.0, +3.0): +3.0;0 +3.0;0 +3.0;0
> (+3.0, NAN): +nan;0 +nan;0 +3.0;0
> ( NAN, +3.0): +3.0;0 +3.0;0 +3.0;0
> ( NAN, NAN): +nan;0 +nan;0 +nan;0
> (+3.0, SNAN): +nan;1 +nan;1 +nan;1
> (SNAN, +3.0): +3.0;1 +3.0;1 +nan;1
> (SNAN, SNAN): +nan;1 +nan;1 +nan;1
> --
> Without -ffast-math, fmin() matches xsmindp.
> With -ffast-math, fmin() matches xsmincdp.
Nice test case! We probably can note this matching to xs{min,max}dp as one
small "Programming Note" in ISA document.
next prev parent reply other threads:[~2022-04-28 3:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 16:21 [Bug target/103605] New: " pc at gcc dot gnu.org
2021-12-07 16:21 ` [Bug target/103605] " pc at gcc dot gnu.org
2022-04-26 9:27 ` guihaoc at gcc dot gnu.org
2022-04-26 18:35 ` pc at gcc dot gnu.org
2022-04-26 18:46 ` joseph at codesourcery dot com
2022-04-26 20:45 ` pc at gcc dot gnu.org
2022-04-27 5:32 ` guihaoc at gcc dot gnu.org
2022-04-28 3:22 ` linkw at gcc dot gnu.org [this message]
2022-05-10 12:21 ` segher at gcc dot gnu.org
2023-07-25 2:43 ` cvs-commit at gcc dot gnu.org
2023-08-17 5:26 ` guihaoc 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-103605-4-wBC8QGNt6e@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).