public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/103571] ABI: V2HF, V4HF and V8HFmode argument passing issues
Date: Thu, 16 Dec 2021 18:49:38 +0000 [thread overview]
Message-ID: <bug-103571-4-tZL7yFfCEn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103571-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103571
--- Comment #27 from Uroš Bizjak <ubizjak at gmail dot com> ---
(In reply to Hongtao.liu from comment #17)
> (In reply to Hongtao.liu from comment #16)
> > There're already testcases for vec_extract/vec_set/vec_duplicate, but those
> > testcases are written under TARGET_AVX512FP16, i'll make a copy of them and
> > test them w/o avx512fp16.
>
> Also we can relax condition of extendv*hfv*sf and truncv*sfv*hf to
> avx512vl/f16c so that vect-float16-1.c could be vectorized.
>
> vect-float16-1.c
>
> void
> foo (_Float16 *__restrict__ a, _Float16 *__restrict__ b,
> _Float16 *__restrict__ c)
> {
> for (int i = 0; i < 256; i++)
> a[i] = b[i] + c[i];
> }
This was recently fixed, for -O2 -ftree-vectorize -mfp16c I get:
vpxor %xmm2, %xmm2, %xmm2
vpinsrw $0, (%rsi,%rax), %xmm2, %xmm0
vpinsrw $0, (%rdx,%rax), %xmm2, %xmm1
vcvtph2ps %xmm0, %xmm0
vcvtph2ps %xmm1, %xmm1
vaddss %xmm1, %xmm0, %xmm0
vinsertps $0xe, %xmm0, %xmm0, %xmm0
vcvtps2ph $4, %xmm0, %xmm0
vpextrw $0, %xmm0, (%rdi,%rax)
addq $2, %rax
cmpq $512, %rax
jne .L2
ret
While it would be nice to partially vectorize with vcvtph2ps/vcvtps2ph, the
compiler doesn't reach that far.
next prev parent reply other threads:[~2021-12-16 18:49 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 8:35 [Bug target/103571] New: " ubizjak at gmail dot com
2021-12-06 11:37 ` [Bug target/103571] " crazylht at gmail dot com
2021-12-07 3:05 ` crazylht at gmail dot com
2021-12-07 7:47 ` wwwhhhyyy333 at gmail dot com
2021-12-07 7:54 ` ubizjak at gmail dot com
2021-12-07 8:14 ` crazylht at gmail dot com
2021-12-07 11:04 ` ubizjak at gmail dot com
2021-12-07 11:17 ` ubizjak at gmail dot com
2021-12-08 5:27 ` crazylht at gmail dot com
2021-12-08 7:10 ` ubizjak at gmail dot com
2021-12-08 7:16 ` crazylht at gmail dot com
2021-12-08 14:25 ` ubizjak at gmail dot com
2021-12-08 14:38 ` ubizjak at gmail dot com
2021-12-08 15:05 ` ubizjak at gmail dot com
2021-12-08 15:07 ` ubizjak at gmail dot com
2021-12-09 0:39 ` crazylht at gmail dot com
2021-12-09 0:42 ` crazylht at gmail dot com
2021-12-09 4:15 ` crazylht at gmail dot com
2021-12-09 5:57 ` crazylht at gmail dot com
2021-12-09 7:07 ` crazylht at gmail dot com
2021-12-09 7:21 ` crazylht at gmail dot com
2021-12-09 8:15 ` ubizjak at gmail dot com
2021-12-09 8:36 ` crazylht at gmail dot com
2021-12-14 17:28 ` cvs-commit at gcc dot gnu.org
2021-12-14 18:30 ` ubizjak at gmail dot com
2021-12-16 8:51 ` ubizjak at gmail dot com
2021-12-16 18:35 ` cvs-commit at gcc dot gnu.org
2021-12-16 18:49 ` ubizjak at gmail dot com [this message]
2021-12-16 18:55 ` ubizjak at gmail dot com
2021-12-16 19:22 ` ubizjak at gmail dot com
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-103571-4-tZL7yFfCEn@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).