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 middle-end/111876] bf16 complex mul/div does not work when the target has +fp16 support or when -fexcess-precision=16 is supplied
Date: Sun, 10 Dec 2023 02:32:24 +0000 [thread overview]
Message-ID: <bug-111876-4-EgXFBBWIxS@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
----------------------------------------------------------------------------
Component|target |middle-end
Keywords| |testsuite-fail
--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
I see this failure with `-march=armv9-a+sve2` .
Just for record it is while testing:
FAIL: gcc.dg/torture/bfloat16-complex.c -O0 (test for excess errors)
UNRESOLVED: gcc.dg/torture/bfloat16-complex.c -O0 compilation failed to
produce executable
FAIL: gcc.dg/torture/bfloat16-complex.c -O1 (test for excess errors)
UNRESOLVED: gcc.dg/torture/bfloat16-complex.c -O1 compilation failed to
produce executable
FAIL: gcc.dg/torture/bfloat16-complex.c -O2 (test for excess errors)
UNRESOLVED: gcc.dg/torture/bfloat16-complex.c -O2 compilation failed to
produce executable
FAIL: gcc.dg/torture/bfloat16-complex.c -O2 -flto -fno-use-linker-plugin
-flto-partition=none (test for excess errors)
UNRESOLVED: gcc.dg/torture/bfloat16-complex.c -O2 -flto
-fno-use-linker-plugin -flto-partition=none compilation failed to produce
executable
FAIL: gcc.dg/torture/bfloat16-complex.c -O2 -flto -fuse-linker-plugin
-fno-fat-lto-objects (test for excess errors)
UNRESOLVED: gcc.dg/torture/bfloat16-complex.c -O2 -flto -fuse-linker-plugin
-fno-fat-lto-objects compilation failed to produce executable
FAIL: gcc.dg/torture/bfloat16-complex.c -O3 -g (test for excess errors)
UNRESOLVED: gcc.dg/torture/bfloat16-complex.c -O3 -g compilation failed to
produce executable
FAIL: gcc.dg/torture/bfloat16-complex.c -Os (test for excess errors)
UNRESOLVED: gcc.dg/torture/bfloat16-complex.c -Os compilation failed to
produce executable
prev parent reply other threads:[~2023-12-10 2:32 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 when the target has +fp16 support iains at gcc dot gnu.org
2023-10-19 18:58 ` [Bug target/111876] aarch64: bf16 complex mul/div does not work " pinskia at gcc dot gnu.org
2023-10-19 19:05 ` 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 ` pinskia at gcc dot gnu.org [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-111876-4-EgXFBBWIxS@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).