public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "alalaw01 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/63870] [Aarch64] [ARM] Errors in use of NEON intrinsics are reported incorrectly
Date: Wed, 10 Dec 2014 11:21:00 -0000	[thread overview]
Message-ID: <bug-63870-4-cFp9lFuoeM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63870-4@http.gcc.gnu.org/bugzilla/>

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

alalaw01 at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |alalaw01 at gcc dot gnu.org

--- Comment #4 from alalaw01 at gcc dot gnu.org ---
(Apologies for out-of-orderness, I missed PRs from logs so adding by hand)

Author: alalaw01
Date: Tue Dec  9 19:52:22 2014
Revision: 218532

https://gcc.gnu.org/viewcvs?rev=218532&root=gcc&view=rev
Log:
[AArch64] Fix ICE on non-constant indices to __builtin_aarch64_im_lane_boundsi

gcc/:

        * config/aarch64/aarch64-builtins.c (aarch64_types_binopv_qualifiers,
        TYPES_BINOPV): Delete.
        (enum aarch64_builtins): Add AARCH64_BUILTIN_SIMD_LANE_CHECK and
        AARCH64_SIMD_PATTERN_START.
        (aarch64_init_simd_builtins): Register
        __builtin_aarch64_im_lane_boundsi; use  AARCH64_SIMD_PATTERN_START.
        (aarch64_simd_expand_builtin): Handle AARCH64_BUILTIN_LANE_CHECK; use
        AARCH64_SIMD_PATTERN_START.

        * config/aarch64/aarch64-simd.md (aarch64_im_lane_boundsi): Delete.
        * config/aarch64/aarch64-simd-builtins.def (im_lane_bound): Delete.

        * config/aarch64/arm_neon.h (__AARCH64_LANE_CHECK): New.
        (__aarch64_vget_lane_f64, __aarch64_vget_lane_s64,
        __aarch64_vget_lane_u64, __aarch64_vset_lane_any, vdupd_lane_f64,
        vdupd_lane_s64, vdupd_lane_u64, vext_f32, vext_f64, vext_p8, vext_p16,
        vext_s8, vext_s16, vext_s32, vext_s64, vext_u8, vext_u16, vext_u32,
        vext_u64, vextq_f32, vextq_f64, vextq_p8, vextq_p16, vextq_s8,
        vextq_s16, vextq_s32, vextq_s64, vextq_u8, vextq_u16, vextq_u32,
        vextq_u64, vmulq_lane_f64): Use __AARCH64_LANE_CHECK.

gcc/testsuite/:

        * gcc.target/aarch64/simd/vset_lane_s16_const_1.c: New test.


  parent reply	other threads:[~2014-12-10 11:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-14 13:52 [Bug target/63870] New: [Aarch64] [ARM] Errors in use of NEON instrinsics " cbaylis at gcc dot gnu.org
2014-11-18 16:21 ` [Bug target/63870] [Aarch64] [ARM] Errors in use of NEON intrinsics " alan.lawrence at arm dot com
2014-11-20 16:27 ` cbaylis at gcc dot gnu.org
2014-11-27 21:06 ` ramana at gcc dot gnu.org
2014-12-09 20:24 ` alalaw01 at gcc dot gnu.org
2014-12-10 11:21 ` alalaw01 at gcc dot gnu.org [this message]
2015-01-14 15:48 ` ktkachov at gcc dot gnu.org
2015-01-14 16:29 ` cbaylis at gcc dot gnu.org
2015-01-15 18:36 ` alalaw01 at gcc dot gnu.org
2015-09-08 19:44 ` alalaw01 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-63870-4-cFp9lFuoeM@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).