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/100637] [i386] Vectorize 4-byte vectors
Date: Fri, 04 Jun 2021 15:38:53 +0000 [thread overview]
Message-ID: <bug-100637-4-IYgHQtiuzm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100637-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100637
--- Comment #9 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:8d7dae0eb366a88a1baba1857ecc54c09e4a520e
commit r12-1215-g8d7dae0eb366a88a1baba1857ecc54c09e4a520e
Author: Uros Bizjak <ubizjak@gmail.com>
Date: Fri Jun 4 17:37:15 2021 +0200
i386: Add init pattern for V2HI vectors [PR100637]
2021-06-03 Uroš Bizjak <ubizjak@gmail.com>
gcc/
PR target/100637
* config/i386/i386-expand.c (ix86_expand_vector_init_duplicate):
Handle V2HI mode.
(ix86_expand_vector_init_general): Ditto.
Use SImode instead of word_mode for logic operations
when GET_MODE_SIZE (mode) < UNITS_PER_WORD.
(expand_vec_perm_even_odd_1): Assert that V2HI mode should be
implemented by expand_vec_perm_1.
(expand_vec_perm_broadcast_1): Assert that V2HI and V4HI modes
should be implemented using standard shuffle patterns.
(ix86_vectorize_vec_perm_const): Handle V2HImode. Add V4HI and
V2HI modes to modes, implementable with shuffle for one operand.
* config/i386/mmx.md (*punpckwd): New insn_and_split pattern.
(*pshufw_1): New insn pattern.
(*vec_dupv2hi): Ditto.
(vec_initv2hihi): New expander.
gcc/testsuite/
PR target/100637
* gcc.dg/vect/slp-perm-9.c (dg-final): Adjust dumps for vect32
targets.
next prev parent reply other threads:[~2021-06-04 15:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 12:19 [Bug target/100637] New: " ubizjak at gmail dot com
2021-05-17 12:24 ` [Bug target/100637] " ubizjak at gmail dot com
2021-05-18 15:28 ` cvs-commit at gcc dot gnu.org
2021-05-20 9:12 ` cvs-commit at gcc dot gnu.org
2021-05-21 6:02 ` cvs-commit at gcc dot gnu.org
2021-05-21 11:16 ` cvs-commit at gcc dot gnu.org
2021-05-27 7:22 ` cvs-commit at gcc dot gnu.org
2021-05-27 12:48 ` cvs-commit at gcc dot gnu.org
2021-06-03 18:06 ` cvs-commit at gcc dot gnu.org
2021-06-04 15:38 ` cvs-commit at gcc dot gnu.org [this message]
2021-06-07 21:00 ` cvs-commit at gcc dot gnu.org
2021-07-05 19:11 ` ubizjak at gmail dot com
2021-07-08 10:21 ` cvs-commit at gcc dot gnu.org
2022-01-12 19:03 ` cvs-commit at gcc dot gnu.org
2022-01-12 19:23 ` 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-100637-4-IYgHQtiuzm@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).