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 tree-optimization/109029] __builtin_signbit for 64bit fp does not vectorize
Date: Fri, 31 Mar 2023 07:19:19 +0000 [thread overview]
Message-ID: <bug-109029-4-GPJySFuUel@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109029-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109029
--- Comment #9 from Hongtao.liu <crazylht at gmail dot com> ---
(In reply to Hongtao.liu from comment #8)
> >
> > One solution is handling it in ix86_builtin_vectorized_function just like
> > other math functions which has different input/output sizes.
>
> Or extend vectorizable_call to handle NARROW/WIDEN cases when output of ifn
> is same-sized vector integer of vectype_in, and do NARROW/WIDEN between
> ifn_output and vectype_out.
>
> 3472 /* For now, we only vectorize functions if a target specific builtin
> 3473 is available. TODO -- in some cases, it might be profitable to
> 3474 insert the calls for pieces of the vector, in order to be able
> 3475 to vectorize other operations in the loop. */
> 3476 fndecl = NULL_TREE;
> 3477 internal_fn ifn = IFN_LAST;
> 3478 tree callee = gimple_call_fndecl (stmt);
> 3479
> 3480 /* First try using an internal function. */
> 3481 tree_code convert_code = ERROR_MARK;
Another alternative it's we can recognize signbit as shift in the vectorizer.
prev parent reply other threads:[~2023-03-31 7:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-05 12:08 [Bug c++/109029] New: std::signbit(double) generiert sehr ineffizienten code g.peterhoff@t-online.de
2023-03-05 12:11 ` [Bug c++/109029] " g.peterhoff@t-online.de
2023-03-05 19:18 ` [Bug tree-optimization/109029] __builtin_signbit for 64bit fp does not vectorize pinskia at gcc dot gnu.org
2023-03-06 8:52 ` rguenth at gcc dot gnu.org
2023-03-31 3:37 ` crazylht at gmail dot com
2023-03-31 4:16 ` crazylht at gmail dot com
2023-03-31 5:47 ` crazylht at gmail dot com
2023-03-31 5:52 ` crazylht at gmail dot com
2023-03-31 6:22 ` crazylht at gmail dot com
2023-03-31 7:19 ` crazylht at gmail dot com [this message]
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-109029-4-GPJySFuUel@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).