public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "evan@coeus-group.com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/95421] New: [AArch64] Missing NEON functions documented on ARM's web site Date: Fri, 29 May 2020 18:11:18 +0000 [thread overview] Message-ID: <bug-95421-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95421 Bug ID: 95421 Summary: [AArch64] Missing NEON functions documented on ARM's web site Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: evan@coeus-group.com Target Milestone: --- Created attachment 48636 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48636&action=edit Full list of missing functions This is a companion to #95399 (which is for the arm headers instead of aarch64). Quite a few functions listed in ARM's documentation (<https://developer.arm.com/architectures/instruction-sets/simd-isas/neon/intrinsics>) don't seem to be included in GCC's AArch64 arm_{neon,bf16,fp16}.h. The attached list of 253 functions was generated by just grepping arm_{neon,bf16,fp16}.h for each function in ARM's documentation so it's possible there are some false positives, but the ones I've checked manually seem correct. I'm also not sure how accurate ARM's documentation is. Several functions are actually present in arm but not aarch64, I'm guessing that will be an easy place to start. Here is that list: vadd_p16 vadd_p64 vadd_p8 vaddq_p128 vaddq_p16 vaddq_p64 vaddq_p8 vceqq_p64 vceqz_p64 vceqzq_p64 vcvt_high_bf16_f32 vcvt_low_bf16_f32 vld2_lane_bf16 vld2q_lane_bf16 vld3_lane_bf16 vld3q_lane_bf16 vld4_lane_bf16 vld4q_lane_bf16 vrndns_f32 vst2_lane_bf16 vst2q_lane_bf16 vst3_lane_bf16 vst3q_lane_bf16 vst3q_lane_p8 vst3q_lane_s8 vst3q_lane_u8 vst4_lane_bf16 vst4q_lane_bf16
next reply other threads:[~2020-05-29 18:11 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-29 18:11 evan@coeus-group.com [this message] 2020-05-29 18:30 ` [Bug target/95421] " evan@coeus-group.com 2020-06-03 9:25 ` clyon at gcc dot gnu.org 2020-09-11 12:40 ` sripar01 at gcc dot gnu.org 2020-09-11 12:56 ` clyon 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-95421-4@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).