public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/114921] Optimization flags cause _Float16 to __bf16 casting to do nothing
Date: Thu, 02 May 2024 11:42:40 +0000 [thread overview]
Message-ID: <bug-114921-4-FVFeHkhBTb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114921-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114921
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org
Keywords| |wrong-code
Ever confirmed|0 |1
Last reconfirmed| |2024-05-02
Status|UNCONFIRMED |ASSIGNED
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed. We vectorize the loop to
<bb 2> [local count: 119292720]:
vect_temp_9.6_3 = MEM <vector(4) _Float16> [(_Float16 *)f_7(D)];
vect__4.7_9 = VIEW_CONVERT_EXPR<vector(4) __bf16>(vect_temp_9.6_3);
MEM <vector(4) __bf16> [(__bf16 *)f_7(D)] = vect__4.7_9;
vect_temp_9.6_17 = MEM <vector(4) _Float16> [(_Float16 *)f_7(D) + 8B];
vect__4.7_18 = VIEW_CONVERT_EXPR<vector(4) __bf16>(vect_temp_9.6_17);
MEM <vector(4) __bf16> [(__bf16 *)f_7(D) + 8B] = vect__4.7_18;
likely because the vectorizer thinks this is a noop conversion, it handles
it via vectorizable_assignment.
next prev parent reply other threads:[~2024-05-02 11:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 10:17 [Bug c++/114921] New: " mat.mcroci at gmail dot com
2024-05-02 11:42 ` rguenth at gcc dot gnu.org [this message]
2024-05-03 6:20 ` [Bug c++/114921] " cvs-commit at gcc dot gnu.org
2024-05-03 7:28 ` [Bug tree-optimization/114921] " cvs-commit at gcc dot gnu.org
2024-05-07 6:26 ` cvs-commit at gcc dot gnu.org
2024-05-29 6:29 ` 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-114921-4-FVFeHkhBTb@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).