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/103861] [i386] vectorize v2qi vectors
Date: Wed, 05 Jan 2022 22:17:36 +0000	[thread overview]
Message-ID: <bug-103861-4-ILxzJO8nvi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103861-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103861

--- 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:c166632bd22d7da66354121502019fc9c92ef07f

commit r12-6273-gc166632bd22d7da66354121502019fc9c92ef07f
Author: Uros Bizjak <ubizjak@gmail.com>
Date:   Wed Jan 5 23:16:34 2022 +0100

    i386: Introduce V2QImode minmax, abs and uavgv2hi3_ceil [PR103861]

    Add V2QImode minmax, abs and uavxv2qi3_ceil operations with SSE registers.

    2022-01-05  Uroš Bizjak  <ubizjak@gmail.com>

    gcc/ChangeLog:

            PR target/103861
            * config/i386/mmx.md (VI_16_32): New mode iterator.
            (VI1_16_32): Ditto.
            (mmxvecsize): Handle V2QI mode.
            (<smaxmin:code><mode>3): Rename from <smaxmin:code>v4qi3.
            Use VI1_16_32 mode iterator.
            (<umaxmin:code><mode>3): Rename from <umaxmin:code>v4qi3.
            Use VI1_16_32 mode iterator.
            (abs<mode>2): Use VI_16_32 mode iterator.
            (uavgv2qi3_ceil): New insn pattern.

    gcc/testsuite/ChangeLog:

            PR target/103861
            * gcc.target/i386/pr103861-3.c: New test.
            * g++.dg/vect/slp-pr98855.cc (dg-final): Check that
            no vectorization using SLP was performed.

  parent reply	other threads:[~2022-01-05 22:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-29 18:09 [Bug target/103861] New: " ubizjak at gmail dot com
2021-12-29 18:13 ` [Bug target/103861] " ubizjak at gmail dot com
2021-12-29 18:15 ` ubizjak at gmail dot com
2021-12-29 18:21 ` ubizjak at gmail dot com
2021-12-29 20:36 ` pinskia at gcc dot gnu.org
2022-01-02 20:13 ` cvs-commit at gcc dot gnu.org
2022-01-04 13:59 ` rguenth at gcc dot gnu.org
2022-01-04 14:14 ` ubizjak at gmail dot com
2022-01-04 18:44 ` cvs-commit at gcc dot gnu.org
2022-01-05 22:17 ` cvs-commit at gcc dot gnu.org [this message]
2022-01-10 20:00 ` cvs-commit at gcc dot gnu.org
2022-01-11 18:24 ` cvs-commit at gcc dot gnu.org
2022-01-12 19:03 ` cvs-commit at gcc dot gnu.org
2022-01-13 19:49 ` cvs-commit at gcc dot gnu.org
2023-10-27  3:28 ` cvs-commit 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-103861-4-ILxzJO8nvi@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).