public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "liuhongt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85048] [missed optimization] vector conversions
Date: Mon, 22 Apr 2024 00:37:56 +0000 [thread overview]
Message-ID: <bug-85048-4-DoSiFjX3p6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-85048-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85048
Hongtao Liu <liuhongt at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |liuhongt at gcc dot gnu.org
--- Comment #14 from Hongtao Liu <liuhongt at gcc dot gnu.org> ---
(In reply to Matthias Kretz (Vir) from comment #13)
> Should I open a new PR for the remaining ((u)int64, 16) <-> (float, 16)
> conversions?
>
> https://godbolt.org/z/x3xPMYKj3
>
> Note that __builtin_convertvector produces the code we want.
>
With -mprefer-vector-width=512, GCC generate produces the same code.
Default tuning for -march=skylake-avx512 is -mprefer-vector-width=256.
next prev parent reply other threads:[~2024-04-22 0:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-85048-4@http.gcc.gnu.org/bugzilla/>
2023-03-21 20:07 ` mkretz at gcc dot gnu.org
2023-03-22 1:25 ` crazylht at gmail dot com
2023-03-22 1:40 ` crazylht at gmail dot com
2023-03-22 2:10 ` crazylht at gmail dot com
2023-03-31 1:04 ` cvs-commit at gcc dot gnu.org
2023-03-31 1:07 ` crazylht at gmail dot com
2023-03-31 7:28 ` ubizjak at gmail dot com
2024-04-19 13:49 ` mkretz at gcc dot gnu.org
2024-04-22 0:37 ` liuhongt at gcc dot gnu.org [this message]
2024-04-22 8:21 ` mkretz at gcc dot gnu.org
2024-04-22 11:52 ` liuhongt 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-85048-4-DoSiFjX3p6@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).