[Bug target/101893] New: There is no vgbbd on p7

[Bug target/101893] New: There is no vgbbd on p7

[segher at gcc dot gnu.org]

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

            Bug ID: 101893
           Summary: There is no vgbbd on p7
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: segher at gcc dot gnu.org
  Target Milestone: ---

FAIL: gcc.target/powerpc/sse4_1-phminposuw.c (test for excess errors)
Excess errors:
/home/segher/build/tot-master/gcc/include/smmintrin.h:103:3: error: AltiVec
argument passed to unprototyped function

That line is

  __charmask = vec_gb (__charmask);

This is on a power7, so that instruction does not exist (and neither does
the builtin).

[Bug target/101893] There is no vgbbd on p7

[pc at us dot ibm.com]

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

--- Comment #1 from Paul Clarke <pc at us dot ibm.com> ---
I'll take ownership of this, except I'm not sure how to effect that.

The fix has been posted
https://gcc.gnu.org/pipermail/gcc-patches/2021-August/577023.html, and awaits
reviews/approval.

[Bug target/101893] There is no vgbbd on p7

[cvs-commit at gcc dot gnu.org]

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

--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Paul Clarke <pc@gcc.gnu.org>:

https://gcc.gnu.org/g:3cfbe5dc08b574bccc398256946cc03e2a767329

commit r12-4514-g3cfbe5dc08b574bccc398256946cc03e2a767329
Author: Paul A. Clarke <pc@us.ibm.com>
Date:   Mon Aug 9 13:08:25 2021 -0500

    rs6000: Guard some x86 intrinsics implementations

    Some compatibility implementations of x86 intrinsics include
    Power intrinsics which require POWER8.  Guard them.

    emmintrin.h:
    - _mm_cmpord_pd: Remove code which was ostensibly for pre-POWER8,
      but which indeed depended on POWER8 (vec_cmpgt(v2du)/vcmpgtud).
      The "POWER8" version works fine on pre-POWER8.
    - _mm_mul_epu32: vec_mule(v4su) uses vmuleuw.
    pmmintrin.h:
    - _mm_movehdup_ps: vec_mergeo(v4su) uses vmrgow.
    - _mm_moveldup_ps: vec_mergee(v4su) uses vmrgew.
    smmintrin.h:
    - _mm_cmpeq_epi64: vec_cmpeq(v2di) uses vcmpequd.
    - _mm_mul_epi32: vec_mule(v4si) uses vmuluwm.
    - _mm_cmpgt_epi64: vec_cmpgt(v2di) uses vcmpgtsd.
    tmmintrin.h:
    - _mm_sign_epi8: vec_neg(v4si) uses vsububm.
    - _mm_sign_epi16: vec_neg(v4si) uses vsubuhm.
    - _mm_sign_epi32: vec_neg(v4si) uses vsubuwm.
      Note that the above three could actually be supported pre-POWER8,
      but current GCC does not support them before POWER8.
    - _mm_sign_pi8: depends on _mm_sign_epi8.
    - _mm_sign_pi16: depends on _mm_sign_epi16.
    - _mm_sign_pi32: depends on _mm_sign_epi32.

    sse4_2-pcmpgtq.c:
    - _mm_cmpgt_epi64: vec_cmpeq(v2di) uses vcmpequd.

    2021-10-19  Paul A. Clarke  <pc@us.ibm.com>

    gcc
            PR target/101893
            PR target/102719
            * config/rs6000/emmintrin.h: Guard POWER8 intrinsics.
            * config/rs6000/pmmintrin.h: Same.
            * config/rs6000/smmintrin.h: Same.
            * config/rs6000/tmmintrin.h: Same.

    gcc/testsuite
            * gcc.target/powerpc/sse4_2-pcmpgtq.c: Tighten dg constraints
            to minimally Power8.

[Bug target/101893] There is no vgbbd on p7

[bergner at gcc dot gnu.org]

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

Peter Bergner <bergner at gcc dot gnu.org> changed:

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

--- Comment #3 from Peter Bergner <bergner at gcc dot gnu.org> ---
So this looks fixed and we can mark it RESOLVED / FIXED?

[Bug target/101893] There is no vgbbd on p7

[segher at gcc dot gnu.org]

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

Segher Boessenkool <segher at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #4 from Segher Boessenkool <segher at gcc dot gnu.org> ---
Yeah.  You could have done that yourself :-)

The bug can always be reopened, if it turns out not to be fixed.