public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mgretton at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/51534] Bad code gen for vcgtq_u32 NEON intrinsic
Date: Tue, 28 Feb 2012 16:15:00 -0000	[thread overview]
Message-ID: <bug-51534-4-klLUddvhyr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51534-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51534

--- Comment #3 from mgretton at gcc dot gnu.org 2012-02-28 16:14:03 UTC ---
Author: mgretton
Date: Tue Feb 28 16:13:52 2012
New Revision: 184629

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=184629
Log:
    PR target/51534
    * gcc/config/arm/arm.c (neon_builtin_data): Add entries for vcgeu
    and vcgtu.
    * gcc/config/arm/arm_neon.h: Regenerate.
    * gcc/config/arm/neon.md (unspec): Add UNSPEC_VCGEU, and UNSPEC_VCGTU.
    (neon_vcgeu): New insn.
    (neon_vcgtu): Likewise.
    * gcc/config/arm/neon.ml (s_8_32, u_8_32): New lists.
    (ops): Unsigned comparison intrinsics call a different
    builtin.
    * gcc/testsuite/gcc.target/arm/neon/pr51534.c: New testcase.

Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/config/arm/arm.c
    trunk/gcc/config/arm/arm_neon.h
    trunk/gcc/config/arm/neon.md
    trunk/gcc/config/arm/neon.ml
    trunk/gcc/testsuite/ChangeLog


  parent reply	other threads:[~2012-02-28 16:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-13 19:29 [Bug target/51534] New: " rmansfield at qnx dot com
2011-12-13 19:53 ` [Bug target/51534] " rmansfield at qnx dot com
2011-12-14 15:01 ` rearnsha at gcc dot gnu.org
2012-02-28 16:15 ` mgretton at gcc dot gnu.org [this message]
2012-02-28 16:19 ` mgretton at gcc dot gnu.org
2014-08-10 16:46 ` rmansfield at qnx dot com
2023-03-03 19:10 ` cvs-commit 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-51534-4-klLUddvhyr@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).