public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/95399] [ARM, AArch64] 32/64-bit vcvtnq_* functions are missing Date: Fri, 29 May 2020 08:13:34 +0000 [thread overview] Message-ID: <bug-95399-4-hBgtd7c7AI@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 ktkachov at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ktkachov at gcc dot gnu.org --- Comment #1 from ktkachov at gcc dot gnu.org --- Hmm... I see them present for aarch64 and even in the gotbolt setup you provided (use ARM64 gcc 8.2) They do seem to be missing from arm though indeed
next prev parent reply other threads:[~2020-05-29 8:13 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-29 0:00 [Bug target/95399] New: " evan@coeus-group.com 2020-05-29 8:13 ` ktkachov at gcc dot gnu.org [this message] 2020-05-29 16:33 ` [Bug target/95399] " 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-hBgtd7c7AI@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).