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/107432] __builtin_convertvector generates inefficient code
Date: Fri, 28 Oct 2022 05:22:22 +0000 [thread overview]
Message-ID: <bug-107432-4-jl3g5M1nlj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107432-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107432
--- Comment #5 from Hongtao.liu <crazylht at gmail dot com> ---
> It's lowered by pass_lower_vector, ideally, can we use truncmn2 in
> expand_VEC_CONVERT if src is bigger integer mode than dest.
Currently, expand_vector_conversion uses VEC_PACK_TRUNC_EXPR
---------------cut begins------------------------
else if (modifier == NARROW)
{
switch (code)
{
CASE_CONVERT:
code1 = VEC_PACK_TRUNC_EXPR;
optab1 = optab_for_tree_code (code1, arg_type, optab_default);
break;
---------------Cut ends------------------------
But BB vectorizer can do the right thing for
void
foo (long long* a, int* b)
{
b[0] = a[0];
b[1] = a[1];
b[2] = a[2];
b[3] = a[3];
}
vmovdqu ymm0, YMMWORD PTR [rdi]
vpmovqd XMMWORD PTR [rsi], ymm0
vzeroupper
ret
vect__1.5_16 = MEM <vector(4) long long int> [(long long int *)a_10(D)];
vect__2.6_18 = (vector(4) int) vect__1.5_16;
# DEBUG BEGIN_STMT
# DEBUG BEGIN_STMT
# DEBUG BEGIN_STMT
MEM <vector(4) int> [(int *)b_11(D)] = vect__2.6_18;
return;
Guess expand_vector_conversion can be optimized.
next prev parent reply other threads:[~2022-10-28 5:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 10:02 [Bug c++/107432] New: " g.peterhoff@t-online.de
2022-10-27 15:12 ` [Bug target/107432] " pinskia at gcc dot gnu.org
2022-10-27 16:14 ` g.peterhoff@t-online.de
2022-10-28 3:33 ` crazylht at gmail dot com
2022-10-28 3:36 ` crazylht at gmail dot com
2022-10-28 5:22 ` crazylht at gmail dot com [this message]
2022-10-28 5:33 ` crazylht at gmail dot com
2022-10-28 6:55 ` crazylht at gmail dot com
2022-10-28 11:41 ` rguenth at gcc dot gnu.org
2022-10-31 13:02 ` rsandifo 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-107432-4-jl3g5M1nlj@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).