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/95471] vrndvq_f32 not supported on armv8 Date: Tue, 02 Jun 2020 17:50:50 +0000 [thread overview] Message-ID: <bug-95471-4-7hUeO4t1sk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95471-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95471 --- Comment #2 from Evan Nemerson <evan@coeus-group.com> --- In that case shouldn't the header be adjusted to not define the vrndvq_f32 function unless it is enabled? It is already guarded by a check for __ARM_ARCH >= 8 (see <https://github.com/gcc-mirror/gcc/blob/95827968e5f3e472bbef0ad8b65b0a7537c9cee3/gcc/config/arm/arm_neon.h#L1757>, but obviously that isn't sufficient. If nothing else it would help document the actual requirements, which would be great since the flags and macros on ARM are a bit of a mess.
prev parent reply other threads:[~2020-06-02 17:50 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-02 1:50 [Bug target/95471] New: " evan@coeus-group.com 2020-06-02 8:43 ` [Bug target/95471] " ktkachov at gcc dot gnu.org 2020-06-02 17:50 ` evan@coeus-group.com [this message]
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-95471-4-7hUeO4t1sk@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).