public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/106910] roundss not vectorized
Date: Thu, 15 Sep 2022 09:35:34 +0000 [thread overview]
Message-ID: <bug-106910-4-9h7xXVDU7e@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 #4 from Hongtao.liu <crazylht at gmail dot com> ---
> The vectorizer would go the direct internal fn way for those, querying the
> floor optab but the x86 backend only has scalar modes supported for the
> rounding optabs.
For CFN_BUILT_IN_ICEIL, the modifier is narrow, and currently vectorizable_call
require op_in and op_out to be simple_integer_narrowing, which means it fails
to go the direct internal fn way.
---------cut from vectorizable_call-----------
tree_code convert_code = ERROR_MARK;
if (cfn != CFN_LAST
&& (modifier == NONE
|| (modifier == NARROW
&& simple_integer_narrowing (vectype_out, vectype_in,
&convert_code))))
ifn = vectorizable_internal_function (cfn, callee, vectype_out,
vectype_in);
-----------cut end----------------------
Similar for CFN_BUILT_IN_LCEIL under 32-bit target.
For 64-bit target CFN_BUILT_IN_LCEIL, CFN_BUILT_IN_LLCEIL will go the direct
internal fn way, add lceilmn2 expanders works.
Not sure whether vectorizable_call should be extended or just leave
CFN_BUILT_IN_ICEIL/IFLOOR/IRINT/IROUND part in
ix86_builtin_vectorized_function.
next prev parent reply other threads:[~2022-09-15 9:35 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 [this message]
2022-09-15 11:40 ` rguenther at suse dot de
2022-09-16 7:45 ` cvs-commit at gcc dot gnu.org
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-9h7xXVDU7e@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).