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

            Bug ID: 104724
           Summary: gcc.target/i386/avx512fp16-vcvtsi2sh-1b.c etc. FAIL
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: ro at gcc dot gnu.org
                CC: crazylht at gmail dot com
  Target Milestone: ---
            Target: i?86-pc-solaris2.11, x86_64-pc-solaris2.11

A couple of tests FAIL on Solaris/x86 since their introduction:

+FAIL: gcc.target/i386/avx512fp16-vcvtsi2sh-1b.c (test for excess errors)
+UNRESOLVED: gcc.target/i386/avx512fp16-vcvtsi2sh-1b.c compilation failed to
produce executable

+FAIL: gcc.target/i386/avx512fp16-vcvtusi2sh-1b.c (test for excess errors)
+UNRESOLVED: gcc.target/i386/avx512fp16-vcvtusi2sh-1b.c compilation failed to
produce executable

  32 and 64-bit x86

+FAIL: gcc.target/i386/avx512fp16-vcvtsi2sh64-1b.c (test for excess errors)
+UNRESOLVED: gcc.target/i386/avx512fp16-vcvtsi2sh64-1b.c compilation failed to
produce executable
+FAIL: gcc.target/i386/avx512fp16-vcvtusi2sh-1b.c (test for excess errors)
+UNRESOLVED: gcc.target/i386/avx512fp16-vcvtusi2sh-1b.c compilation failed to
produce executable
+FAIL: gcc.target/i386/avx512fp16-vcvtusi2sh64-1b.c (test for excess errors)
+UNRESOLVED: gcc.target/i386/avx512fp16-vcvtusi2sh64-1b.c compilation failed to
produce executable

  64-bit x86

The failure mode is always the same:

Excess errors:
/vol/gcc/src/hg/master/local/gcc/testsuite/gcc.target/i386/avx512fp16-vcvtsi2sh-1b.c:12:33:
error: unknown type name '__int64_t'; did you mean 'uint64_t'?
/vol/gcc/src/hg/master/local/gcc/testsuite/gcc.target/i386/avx512fp16-vcvtsi2sh-1b.c:33:3:
warning: implicit declaration of function 'emulate_vcvtsi2sh'
[-Wimplicit-function-declaration]

I believe the tests should just avoid the non-standard __int64_t type and
instead
include <stdint.h> and use int64_t like many other tests.do.

Reply via email to