public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/97349] Incorrect types for some AArch64 Neon vdupq_n_<...> intrinsics
Date: Tue, 13 Oct 2020 10:31:17 +0000	[thread overview]
Message-ID: <bug-97349-4-OspJXxYmNG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97349-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97349

--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-9 branch has been updated by Kyrylo Tkachov
<ktkachov@gcc.gnu.org>:

https://gcc.gnu.org/g:b9c1ca3e2fc84b40dc2ab70d12064e3d0eb8abdd

commit r9-8992-gb9c1ca3e2fc84b40dc2ab70d12064e3d0eb8abdd
Author: Kyrylo Tkachov <kyrylo.tkachov@arm.com>
Date:   Fri Oct 9 10:34:15 2020 +0100

    PR target/97349 AArch64: Incorrect types for some Neon vdupq_n_<...>
intrinsics

    This patch fixes the PR by adjusting the input types of the intrinsic
    prototypes to the ones mandated by ACLE
    Turns out the tests in the testsuite were already using the correct
    ones, but implicit conversions hid the bug...

    Bootstrapped and tested on aarch64-none-linux-gnu.

    gcc/
            PR target/97349
            * config/aarch64/arm_neon.h (vdupq_n_p8, vdupq_n_p16,
            vdupq_n_p64, vdupq_n_s8, vdupq_n_s16, vdupq_n_u8, vdupq_n_u16):
            Fix argument type.

    gcc/testsuite/
            PR target/97349
            * gcc.target/aarch64/simd/pr97349.c: New test.

    (cherry picked from commit 8a3da2e6060ff0f61dae6aaada716e2c67f3d54f)

  parent reply	other threads:[~2020-10-13 10:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-09  9:15 [Bug target/97349] New: Incorrect types for some " david.spickett at linaro dot org
2020-10-09  9:47 ` [Bug target/97349] Incorrect types for some Arm " ktkachov at gcc dot gnu.org
2020-10-09 16:31 ` [Bug target/97349] Incorrect types for some AArch64 " ktkachov at gcc dot gnu.org
2020-10-10 15:11 ` ktkachov at gcc dot gnu.org
2020-10-12 10:55 ` cvs-commit at gcc dot gnu.org
2020-10-12 16:38 ` cvs-commit at gcc dot gnu.org
2020-10-13 10:31 ` cvs-commit at gcc dot gnu.org [this message]
2020-10-13 11:27 ` cvs-commit at gcc dot gnu.org
2020-10-13 11:28 ` ktkachov 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-97349-4-OspJXxYmNG@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).