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 target/106012] rsqrtps and rcpps instructions generated even if -fno-reciprocal-math specified
Date: Mon, 20 Jun 2022 10:13:41 +0000 [thread overview]
Message-ID: <bug-106012-4-hcopS0Uct7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106012-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106012
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target| |x86_64-*-*
Component|tree-optimization |target
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to vincenzo Innocente from comment #3)
> Thanks for the suggestion.
>
> -fno-reciprocal-math does indeed inhibit scalar reciprocal instructions.
>
> NOT in vectorized loop though.
>
> see
>
> https://godbolt.org/z/9eMb4Tjee
For that you need -mno-recip as well ... (here it's the target expanding
the division). Maybe the target should take -fno-reciprocal-math as
enabling -mno-recip.
next prev parent reply other threads:[~2022-06-20 10:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 9:17 [Bug target/106012] New: rsqrtss instruction generated even if -mno-recip specified vincenzo.innocente at cern dot ch
2022-06-17 11:16 ` [Bug tree-optimization/106012] " ubizjak at gmail dot com
2022-06-18 20:20 ` pinskia at gcc dot gnu.org
2022-06-19 9:18 ` [Bug tree-optimization/106012] rsqrtps and rcpps instructiona generated even if -fno-reciprocal-math specified vincenzo.innocente at cern dot ch
2022-06-20 10:13 ` rguenth at gcc dot gnu.org [this message]
2022-06-20 10:15 ` [Bug target/106012] rsqrtps and rcpps instructions " rguenth at gcc dot gnu.org
2022-12-20 14:23 ` vincenzo.innocente at cern dot ch
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-106012-4-hcopS0Uct7@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).