public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug target/96313] New: [AArch64] vqmovun* return types should be unsigned
@ 2020-07-24 20:20 evan@coeus-group.com
  2020-07-27 15:10 ` [Bug target/96313] " rearnsha at gcc dot gnu.org
                   ` (9 more replies)
  0 siblings, 10 replies; 11+ messages in thread
From: evan@coeus-group.com @ 2020-07-24 20:20 UTC (permalink / raw)
  To: gcc-bugs

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

            Bug ID: 96313
           Summary: [AArch64] vqmovun* return types should be unsigned
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: evan@coeus-group.com
  Target Milestone: ---

GCC has signed return values for the vqmovun* functions, but they should be
unsigned.  See
https://developer.arm.com/architectures/instruction-sets/simd-isas/neon/intrinsics?search=vqmovun

Trivial test case:

  #include <arm_neon.h>

  uint16_t foo(int32_t v) {
    return vqmovuns_s32(v);
  }

^ permalink raw reply	[flat|nested] 11+ messages in thread

end of thread, other threads:[~2020-10-08 17:24 UTC | newest]

Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-07-24 20:20 [Bug target/96313] New: [AArch64] vqmovun* return types should be unsigned evan@coeus-group.com
2020-07-27 15:10 ` [Bug target/96313] " rearnsha at gcc dot gnu.org
2020-07-27 15:42 ` jgreenhalgh at gcc dot gnu.org
2020-09-17  9:46 ` david.spickett at linaro dot org
2020-09-17  9:46 ` david.spickett at linaro dot org
2020-09-30 11:03 ` cvs-commit at gcc dot gnu.org
2020-09-30 11:07 ` ktkachov at gcc dot gnu.org
2020-10-08 14:59 ` cvs-commit at gcc dot gnu.org
2020-10-08 16:10 ` cvs-commit at gcc dot gnu.org
2020-10-08 17:22 ` cvs-commit at gcc dot gnu.org
2020-10-08 17:24 ` ktkachov at gcc dot gnu.org

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).