public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/109254] Bug in gcc (13.0.1) support for ARM SVE, which randomly modifies the prediction register Date: Thu, 23 Mar 2023 17:13:57 +0000 [thread overview] Message-ID: <bug-109254-4-MleJvneBy0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109254-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109254 --- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> --- And --- gcc/config/aarch64/aarch64.cc.jj 2023-03-13 00:11:52.328213351 +0100 +++ gcc/config/aarch64/aarch64.cc 2023-03-23 16:57:29.957866005 +0100 @@ -7388,6 +7388,9 @@ aarch64_function_value_regno_p (const un if (regno >= V0_REGNUM && regno < V0_REGNUM + HA_MAX_NUM_FLDS) return TARGET_FLOAT; + if (regno == P0_REGNUM) + return TARGET_SVE; + return false; } Or can one actually return in more than p0? Tried struct S { svbool_t a, b; }; but that is rejected...
next prev parent reply other threads:[~2023-03-23 17:13 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-23 3:14 [Bug target/109254] New: " wumingchuan1992 at foxmail dot com 2023-03-23 3:23 ` [Bug target/109254] " pinskia at gcc dot gnu.org 2023-03-23 14:43 ` jakub at gcc dot gnu.org 2023-03-23 16:08 ` jakub at gcc dot gnu.org 2023-03-23 17:13 ` jakub at gcc dot gnu.org [this message] 2023-03-24 12:24 ` jakub at gcc dot gnu.org 2023-03-27 7:53 ` pinskia at gcc dot gnu.org 2023-04-01 6:58 ` cvs-commit at gcc dot gnu.org 2023-04-03 13:18 ` jakub at gcc dot gnu.org 2024-02-28 6:48 ` 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-109254-4-MleJvneBy0@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).