public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sripar01 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/95421] [AArch64] Missing NEON functions documented on ARM's web site
Date: Fri, 11 Sep 2020 12:40:19 +0000 [thread overview]
Message-ID: <bug-95421-4-fBMlfNubRp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95421-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95421
SRINATH PARVATHANENI <sripar01 at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sripar01 at gcc dot gnu.org
--- Comment #3 from SRINATH PARVATHANENI <sripar01 at gcc dot gnu.org> ---
I see following intrinsics for AArch64 already implemented.
vst3q_lane_p8
vst3q_lane_s8
vst3q_lane_u8
__extension__ extern __inline void __attribute__ ((__always_inline__,
__gnu_inline__, __artificial__)) vst3q_lane_p8 (poly8_t *__ptr, poly8x16x3_t
__b, const int __c) { union { poly8x16x3_t __i; __builtin_aarch64_simd_ci __o;
} __temp = { __b }; __builtin_aarch64_st3_lanev16qi ((__builtin_aarch64_simd_qi
*) __ptr, __temp.__o, __c); }
__extension__ extern __inline void __attribute__ ((__always_inline__,
__gnu_inline__, __artificial__)) vst3q_lane_s8 (int8_t *__ptr, int8x16x3_t __b,
const int __c) { union { int8x16x3_t __i; __builtin_aarch64_simd_ci __o; }
__temp = { __b }; __builtin_aarch64_st3_lanev16qi ((__builtin_aarch64_simd_qi
*) __ptr, __temp.__o, __c); }
__extension__ extern __inline void __attribute__ ((__always_inline__,
__gnu_inline__, __artificial__)) vst3q_lane_u8 (uint8_t *__ptr, uint8x16x3_t
__b, const int __c) { union { uint8x16x3_t __i; __builtin_aarch64_simd_ci __o;
} __temp = { __b }; __builtin_aarch64_st3_lanev16qi ((__builtin_aarch64_simd_qi
*) __ptr, __temp.__o, __c); }
next prev parent reply other threads:[~2020-09-11 12:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 18:11 [Bug target/95421] New: " evan@coeus-group.com
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 [this message]
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-fBMlfNubRp@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).