public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "stammark at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/107515] MVE: Generic functions do not accept _Float16 scalars Date: Thu, 10 Nov 2022 17:30:18 +0000 [thread overview] Message-ID: <bug-107515-4-wXv8UwyAGc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107515-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107515 Stam Markianos-Wright <stammark at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at gcc dot gnu.org |stammark at gcc dot gnu.org CC| |stammark at gcc dot gnu.org Last reconfirmed| |2022-11-10 Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #1 from Stam Markianos-Wright <stammark at gcc dot gnu.org> --- Also confirmed on trunk and assigning to myself, because I believe I've found a fix: ``` diff --git a/gcc/config/arm/arm_mve.h b/gcc/config/arm/arm_mve.h index 2d213e12304..ce20a6fcd24 100644 --- a/gcc/config/arm/arm_mve.h +++ b/gcc/config/arm/arm_mve.h @@ -35582,6 +35582,9 @@ enum { short: __ARM_mve_type_int_n, \ int: __ARM_mve_type_int_n, \ long: __ARM_mve_type_int_n, \ + _Float16: __ARM_mve_type_fp_n, \ + __fp16: __ARM_mve_type_fp_n, \ + float: __ARM_mve_type_fp_n, \ double: __ARM_mve_type_fp_n, \ long long: __ARM_mve_type_int_n, \ unsigned char: __ARM_mve_type_int_n, \ ``` Still untested, though, and I'll likely send it to the mailing list within the next week or two (we've got a couple more arm_mve.h changes in the pipeline, so I'll test them all together).
next prev parent reply other threads:[~2022-11-10 17:30 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-03 9:27 [Bug target/107515] New: " kevin.bracey at alifsemi dot com 2022-11-10 17:30 ` stammark at gcc dot gnu.org [this message] 2022-11-16 16:35 ` [Bug target/107515] " kevin.bracey at alifsemi dot com 2022-11-17 16:56 ` stammark at gcc dot gnu.org 2022-11-21 12:24 ` kevin.bracey at alifsemi dot com 2022-11-28 9:12 ` cvs-commit at gcc dot gnu.org 2022-11-29 8:59 ` kevin.bracey at alifsemi dot com 2022-11-29 13:23 ` stammark at gcc dot gnu.org 2022-11-29 13:29 ` kevin.bracey at alifsemi dot com 2022-12-01 18:37 ` stammark at gcc dot gnu.org 2023-01-16 12:52 ` cvs-commit at gcc dot gnu.org 2023-05-18 10:39 ` cvs-commit at gcc dot gnu.org 2023-05-18 10:43 ` cvs-commit at gcc dot gnu.org 2023-05-18 11:06 ` stammark 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-107515-4-wXv8UwyAGc@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).