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/97887] [10/11 Regression] Failure to optimize neg plus div to avoid using x87 floating point stack
Date: Wed, 18 Nov 2020 13:54:20 +0000 [thread overview]
Message-ID: <bug-97887-4-h80DDYWyqn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97887-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97887
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Uroš Bizjak from comment #3)
> (In reply to Richard Biener from comment #2)
> > combine first makes recog pick negsf2_i387_1:
>
> This should have the following insn constraint:
>
> "TARGET_80387 && !(SSE_FLOAT_MODE_P (<MODE>mode) && TARGET_SSE_MATH)"
>
> to hide it from combine in cases where relevant SSE mode is available.
Hmm, it is
;; Changing of sign for FP values is doable using integer unit too.
(define_insn "*<code><mode>2_i387_1"
[(set (match_operand:X87MODEF 0 "register_operand" "=f,!r")
(absneg:X87MODEF
(match_operand:X87MODEF 1 "register_operand" "0,0")))
(clobber (reg:CC FLAGS_REG))]
"TARGET_80387"
"#")
that is not guarded in this way?
next prev parent reply other threads:[~2020-11-18 13:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 9:35 [Bug target/97887] New: " gabravier at gmail dot com
2020-11-18 10:33 ` [Bug target/97887] [10/11 Regression] " rguenth at gcc dot gnu.org
2020-11-18 10:33 ` rguenth at gcc dot gnu.org
2020-11-18 10:42 ` rguenth at gcc dot gnu.org
2020-11-18 12:11 ` ubizjak at gmail dot com
2020-11-18 13:54 ` rguenth at gcc dot gnu.org [this message]
2020-11-18 13:56 ` ubizjak at gmail dot com
2020-11-18 13:58 ` rguenth at gcc dot gnu.org
2020-11-18 15:09 ` ubizjak at gmail dot com
2020-11-19 9:00 ` rguenth 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-97887-4-h80DDYWyqn@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).