public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/111876] aarch64: bf16 complex mul/div does not work when the target has +fp16 support.
Date: Thu, 19 Oct 2023 18:58:58 +0000 [thread overview]
Message-ID: <bug-111876-4-NXgHkXvTLj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111876-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111876
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |wrong-code
Last reconfirmed| |2023-10-19
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
Summary|aarch64: Wrong code for |aarch64: bf16 complex
|bf16 complex mul/div when |mul/div does not work when
|the target has +fp16 |the target has +fp16
|support. |support.
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
This could either be wrong code for not doing the promotion or just missing the
libgcc functions (which could be implemented as doing the promotion).
Either ways confirmed.
next prev parent reply other threads:[~2023-10-19 18:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 9:36 [Bug target/111876] New: aarch64: Wrong code for bf16 complex mul/div " iains at gcc dot gnu.org
2023-10-19 18:58 ` pinskia at gcc dot gnu.org [this message]
2023-10-19 19:05 ` [Bug target/111876] aarch64: bf16 complex mul/div does not work " iains at gcc dot gnu.org
2023-10-19 19:08 ` pinskia at gcc dot gnu.org
2023-10-19 19:17 ` [Bug target/111876] aarch64: bf16 complex mul/div does not work when the target has +fp16 support or when -fexcess-precision=16 is supplied pinskia at gcc dot gnu.org
2023-10-19 22:12 ` [Bug target/111876] " iains at gcc dot gnu.org
2023-12-10 2:32 ` [Bug middle-end/111876] " pinskia 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-111876-4-NXgHkXvTLj@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).