From: Hans-Peter Nilsson <hp@bitrange.com>
To: Alexandre Oliva <oliva@adacore.com>
Cc: gcc-patches@gcc.gnu.org,
Rainer Orth <ro@cebitec.uni-bielefeld.de>,
Mike Stump <mikestump@comcast.net>
Subject: Re: enable sqrt insns for cdce3.c
Date: Tue, 23 Apr 2024 11:38:53 -0400 (EDT) [thread overview]
Message-ID: <alpine.BSF.2.20.16.2404231123070.90228@arjuna.pair.com> (raw)
In-Reply-To: <orsezdn2ti.fsf@lxoliva.fsfla.org>
On Mon, 22 Apr 2024, Alexandre Oliva wrote:
> [Revamped version of this patch, combined with others, to follow]
>
> On Mar 10, 2021, Hans-Peter Nilsson <hp@bitrange.com> wrote:
Time flies...
> > On Wed, 10 Mar 2021, Alexandre Oliva wrote:
> Is mmix a sqrt_insn effective target? proc
> check_effective_target_sqrt_insn in
> gcc/testsuite/lib/target-supports.exp suggests it shouldn't pass, so I'm
> surprised it would still try to run the test despite the added
> /* { dg-require-effective-target sqrt_insn } */ directive.
The effective-target sqrt_insn predicate says "supports hardware
square root instructions" and doesn't make a difference between
sqrtdf2 (double) and sqrtsf3 (float). I'm extrapolating that
the "divine meaning" of the comment is that such an instruction
must be present for all supported floating-point modes for the
predicate to yield true (when the predicate is correctly
implemented).
(We could also fix the predicate description to actually say
"for all floating-point modes" and/or split the predicate into
mode-specific variants, etc. ;-)
MMIX has sqrtdf2 but not sqrtsf2, and the latter is what's used
in cdce3.c.
> cdce3 is supposed to shrink-wrap the sqrtf(x) call into something like
> (x >= 0 ? .SQRT(x) : sqrtf(x)), where .SQRT stands for a square root
> instruction.
...for 32-bit single floats.
> Since we don't know why it still runs for you, I'm keeping the mmix
> explicit skip in the new version of the patch.
Thanks, that does seem like TRT.
brgds, H-P
next prev parent reply other threads:[~2024-04-23 15:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 5:30 Alexandre Oliva
2021-03-10 17:11 ` Hans-Peter Nilsson
2021-03-11 16:04 ` Alexandre Oliva
2024-04-22 9:50 ` Alexandre Oliva
2024-04-23 15:38 ` Hans-Peter Nilsson [this message]
2024-04-28 7:40 ` Alexandre Oliva
2021-03-20 15:20 ` Jeff Law
2024-04-22 9:56 ` [PATCH v2] [testsuite] require sqrt_insn effective target where needed Alexandre Oliva
2024-04-23 8:59 ` Kewen.Lin
2024-04-23 9:14 ` Iain Sandoe
2024-04-28 7:37 ` Alexandre Oliva
2024-04-24 2:15 ` Mike Stump
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=alpine.BSF.2.20.16.2404231123070.90228@arjuna.pair.com \
--to=hp@bitrange.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mikestump@comcast.net \
--cc=oliva@adacore.com \
--cc=ro@cebitec.uni-bielefeld.de \
/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).