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/111867] aarch64: Wrong code for bf16 literal load when the arch support +fp16 Date: Sun, 10 Dec 2023 00:03:22 +0000 [thread overview] Message-ID: <bug-111867-4-SMNgfo3Vte@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111867-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111867 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |testsuite-fail Assignee|unassigned at gcc dot gnu.org |pinskia at gcc dot gnu.org Status|NEW |ASSIGNED --- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> --- FAIL: gcc.dg/torture/bfloat16-basic.c -O0 execution test FAIL: gcc.dg/torture/bfloat16-basic.c -O1 execution test FAIL: gcc.dg/torture/bfloat16-basic.c -O2 execution test FAIL: gcc.dg/torture/bfloat16-basic.c -O3 -g execution test FAIL: gcc.dg/torture/bfloat16-basic.c -Os execution test FAIL: gcc.dg/torture/bfloat16-basic.c -O2 -flto -fno-use-linker-plugin -flto-partition=none execution test FAIL: gcc.dg/torture/bfloat16-basic.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects execution test FAIL: gcc.dg/torture/bfloat16-builtin.c -O0 execution test FAIL: gcc.dg/torture/bfloat16-builtin.c -O1 execution test FAIL: gcc.dg/torture/bfloat16-builtin.c -O2 execution test FAIL: gcc.dg/torture/bfloat16-builtin.c -O3 -g execution test FAIL: gcc.dg/torture/bfloat16-builtin.c -Os execution test FAIL: gcc.dg/torture/bfloat16-builtin.c -O2 -flto -fno-use-linker-plugin -flto-partition=none execution test FAIL: gcc.dg/torture/bfloat16-builtin.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects execution test Fail when tested with `-march=armv9-a+sve2`.
next prev parent reply other threads:[~2023-12-10 0:03 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-18 18:16 [Bug target/111867] New: " iains at gcc dot gnu.org 2023-10-18 18:19 ` [Bug target/111867] " pinskia at gcc dot gnu.org 2023-10-18 18:23 ` pinskia at gcc dot gnu.org 2023-10-18 18:27 ` pinskia at gcc dot gnu.org 2023-10-18 18:45 ` iains at gcc dot gnu.org 2023-10-23 17:54 ` pinskia at gcc dot gnu.org 2023-10-28 22:48 ` pinskia at gcc dot gnu.org 2023-12-10 0:03 ` pinskia at gcc dot gnu.org [this message] 2023-12-10 4:11 ` pinskia at gcc dot gnu.org 2023-12-10 8:56 ` pinskia at gcc dot gnu.org 2023-12-11 16:00 ` cvs-commit at gcc dot gnu.org 2023-12-11 16:01 ` 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-111867-4-SMNgfo3Vte@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: linkBe 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).