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/106910] roundss not vectorized
Date: Fri, 16 Sep 2022 07:45:09 +0000	[thread overview]
Message-ID: <bug-106910-4-Uv2DShkikg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106910-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by hongtao Liu <liuhongt@gcc.gnu.org>:

https://gcc.gnu.org/g:3e8c4b925a9825fdb8c81f47b621f63108894362

commit r13-2694-g3e8c4b925a9825fdb8c81f47b621f63108894362
Author: liuhongt <hongtao.liu@intel.com>
Date:   Thu Sep 15 18:43:16 2022 +0800

    Modernize ix86_builtin_vectorized_function with corresponding expanders.

    For ifloor/lfloor/iceil/lceil/irint/lrint/iround/lround when size of
    in_mode is not equal out_mode, vectorizer doesn't go to internal fn
    way,still left that part in the ix86_builtin_vectorized_function.

    Remove others builtins and add corresponding expanders.

    gcc/ChangeLog:

            PR target/106910
            * config/i386/i386-builtins.cc
            (ix86_builtin_vectorized_function): Modernized with
            corresponding expanders.
            * config/i386/sse.md (lrint<mode><sseintvecmodelower>2): New
            expander.
            (floor<mode>2): Ditto.
            (lfloor<mode><sseintvecmodelower>2): Ditto.
            (ceil<mode>2): Ditto.
            (lceil<mode><sseintvecmodelower>2): Ditto.
            (btrunc<mode>2): Ditto.
            (lround<mode><sseintvecmodelower>2): Ditto.
            (exp2<mode>2): Ditto.

  parent reply	other threads:[~2022-09-16  7:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-12 16:15 [Bug c++/106910] New: " pilarlatiesa at gmail dot com
2022-09-12 16:35 ` [Bug target/106910] " pinskia at gcc dot gnu.org
2022-09-13  6:31 ` rguenth at gcc dot gnu.org
2022-09-13  7:30 ` crazylht at gmail dot com
2022-09-15  9:35 ` crazylht at gmail dot com
2022-09-15 11:40 ` rguenther at suse dot de
2022-09-16  7:45 ` cvs-commit at gcc dot gnu.org [this message]
2022-09-20  6:54 ` cvs-commit at gcc dot gnu.org
2022-09-20  7:00 ` crazylht at gmail dot com
2022-09-21 10:44 ` pilarlatiesa at gmail dot com
2022-09-22  1:09 ` crazylht at gmail dot com
2022-09-22  1:27 ` crazylht at gmail dot com
2022-09-22  7:45 ` pilarlatiesa at gmail dot com
2022-09-22  7:52 ` crazylht 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-106910-4-Uv2DShkikg@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).