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/95399] New: [ARM, AArch64] 32/64-bit vcvtnq_* functions are missing
Date: Fri, 29 May 2020 00:00:25 +0000 [thread overview]
Message-ID: <bug-95399-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95399
Bug ID: 95399
Summary: [ARM, AArch64] 32/64-bit vcvtnq_* functions are
missing
Product: gcc
Version: 10.1.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: evan@coeus-group.com
Target Milestone: ---
Documentation:
https://developer.arm.com/architectures/instruction-sets/simd-isas/neon/intrinsics?search=vcvtnq
Clang supports them: https://godbolt.org/z/xsMfSz
It looks like vcvtnq_s32_f32, vcvtnq_u32_f32, vcvtnq_s64_f64, and
vcvtnq_u64_f64 are all missing, though vcvtnq_s16_f16 and vcvtnq_u16_f16 are
present.
next reply other threads:[~2020-05-29 0:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 0:00 evan@coeus-group.com [this message]
2020-05-29 8:13 ` [Bug target/95399] " ktkachov at gcc dot gnu.org
2020-05-29 16:33 ` evan@coeus-group.com
2020-05-29 16:37 ` [Bug target/95399] [ARM] " ktkachov at gcc dot gnu.org
2020-05-29 18:34 ` evan@coeus-group.com
2020-06-03 9:24 ` 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-95399-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: 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).