public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/103571] ABI: V2HF, V4HF and V8HFmode argument passing issues
Date: Tue, 14 Dec 2021 17:28:31 +0000 [thread overview]
Message-ID: <bug-103571-4-9KroNkazKQ@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 #23 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Uros Bizjak <uros@gcc.gnu.org>:
https://gcc.gnu.org/g:7a54d3deecf967029f18aa5ed1fcbdb752e213b9
commit r12-5966-g7a54d3deecf967029f18aa5ed1fcbdb752e213b9
Author: Uros Bizjak <ubizjak@gmail.com>
Date: Tue Dec 14 18:27:22 2021 +0100
i386: Implement VxHF vector set/insert/extract with lower ABI levels
This is a preparation patch that moves VxHF vector set/insert/extract
expansions from AVX512FP16 ABI to lower ABIs. There are no functional
changes for -mavx512fp16 and a follow-up patch is needed to actually
enable VxHF vector modes for lower ABIs.
2021-12-14 Uroš Bizjak <ubizjak@gmail.com>
gcc/ChangeLog:
PR target/103571
* config/i386/i386-expand.c (ix86_expand_vector_init_duplicate)
<case E_V8HFmode>: Implement for TARGET_SSE2.
<case E_V16HFmode>: Implement for TARGET_AVX.
<case E_V32HFmode>: Implement for TARGET_AVX512F.
(ix86_expand_vector_set_var): Handle V32HFmode
without TARGET_AVX512BW.
(ix86_expand_vector_extract)
<case E_V8HFmode>: Implement for TARGET_SSE2.
<case E_V16HFmode>: Implement for TARGET_AVX.
<case E_V32HFmode>: Implement for TARGET_AVX512BW.
(expand_vec_perm_broadcast_1) <case E_V8HFmode>: New.
* config/i386/sse.md (VI12HF_AVX512VL): Remove
TARGET_AVX512FP16 condition.
(V): Ditto.
(V_256_512): Ditto.
(avx_vbroadcastf128_<mode>): Use V_256H mode iterator.
next prev parent reply other threads:[~2021-12-14 17:28 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 [this message]
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
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-9KroNkazKQ@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).