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/85048] [missed optimization] vector conversions
Date: Wed, 22 Mar 2023 01:40:20 +0000 [thread overview]
Message-ID: <bug-85048-4-wjEQEOLOjl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-85048-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85048
--- Comment #8 from Hongtao.liu <crazylht at gmail dot com> ---
(In reply to Hongtao.liu from comment #7)
> Yes, Looks like the pattern name is misdefined.
> it shoud be fixuns_trunc, but we have ufix_trunc.
No, we have the right name but generate extra instructions for uns.
8012(define_expand "fixuns_trunc<mode><sseintvecmodelower>2"
8013 [(match_operand:<sseintvecmode> 0 "register_operand")
8014 (match_operand:VF1 1 "register_operand")]
8015 "TARGET_SSE2"
8016{
8017 if (<MODE>mode == V16SFmode)
8018 emit_insn (gen_ufix_truncv16sfv16si2 (operands[0],
8019 operands[1]));
8020 else
8021 {
8022 rtx tmp[3];
8023 tmp[0] = ix86_expand_adjust_ufix_to_sfix_si (operands[1], &tmp[2]);
8024 tmp[1] = gen_reg_rtx (<sseintvecmode>mode);
8025 emit_insn (gen_fix_trunc<mode><sseintvecmodelower>2 (tmp[1],
tmp[0]));
8026 emit_insn (gen_xor<sseintvecmodelower>3 (operands[0], tmp[1],
tmp[2]));
8027 }
8028 DONE;
next prev parent reply other threads:[~2023-03-22 1:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-85048-4@http.gcc.gnu.org/bugzilla/>
2023-03-21 20:07 ` mkretz at gcc dot gnu.org
2023-03-22 1:25 ` crazylht at gmail dot com
2023-03-22 1:40 ` crazylht at gmail dot com [this message]
2023-03-22 2:10 ` crazylht at gmail dot com
2023-03-31 1:04 ` cvs-commit at gcc dot gnu.org
2023-03-31 1:07 ` crazylht at gmail dot com
2023-03-31 7:28 ` ubizjak at gmail dot com
2024-04-19 13:49 ` mkretz at gcc dot gnu.org
2024-04-22 0:37 ` liuhongt at gcc dot gnu.org
2024-04-22 8:21 ` mkretz at gcc dot gnu.org
2024-04-22 11:52 ` liuhongt 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-85048-4-wjEQEOLOjl@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).