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] [ARM] 32/64-bit vcvtnq_* functions are missing
Date: Fri, 29 May 2020 18:34:20 +0000 [thread overview]
Message-ID: <bug-95399-4-tbjvNTFIEF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95399-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95399
Evan Nemerson <evan@coeus-group.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #48635|0 |1
is obsolete| |
--- Comment #4 from Evan Nemerson <evan@coeus-group.com> ---
Created attachment 48637
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48637&action=edit
List of functions missing from 32-bit arm_{neon,fp16,bf16}.h
Sure, I just filed #95421 for AArch64.
Thanks for the note about arm_fp16.h and arm_bf16.h; I hadn't realized those
functions were in separate headers. That bring the total down to 264
functions, of which 236 are present in the AArch64 version. Here is the
updated list.
next prev parent reply other threads:[~2020-05-29 18:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 0:00 [Bug target/95399] New: [ARM, AArch64] " evan@coeus-group.com
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 [this message]
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-tbjvNTFIEF@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).