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

Carl Love <carll at gcc dot gnu.org> changed:

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

--- Comment #3 from Carl Love <carll at gcc dot gnu.org> ---
So, with a little archaeological digging......

Looks like the patch was committed to mainline on 6/8/2021 as follows:

 From db042e1603db5057314c404eded73c45f60ad2d6 Mon Sep 17 00:00:00 2001
From: Carl Love <c...@us.ibm.com>
Date: Mon, 3 Feb 2020 14:41:42 -0600
Subject: [PATCH] RS6000 Add 128-bit Binary Integer sign extend operations

This patch adds the 128-bit sign extension instruction support and
corresponding builtin support.

RS6000 Add 128-bit Binary Integer sign extend operations

2021-06-08  Carl Love  <c...@us.ibm.com>

gcc/ChangeLog

        * config/rs6000/altivec.h (vec_signextll, vec_signexti, vec_signextq):
        Add define for new builtins.
        * config/rs6000/altivec.md(altivec_vreveti2): Add define_expand.
        * config/rs6000/rs6000-builtin.def (VSIGNEXTI, VSIGNEXTLL):  Add
        overloaded builtin definitions.
        (VSIGNEXTSB2W, VSIGNEXTSH2W, VSIGNEXTSB2D, VSIGNEXTSH2D,VSIGNEXTSW2D,
        VSIGNEXTSD2Q):  Add builtin expansions.
        (SIGNEXT): Add P10 overload definition.
        * config/rs6000/rs6000-call.c (P9V_BUILTIN_VEC_VSIGNEXTI,
P9V_BUILTIN_VEC_VSIGNEXTLL,
        P10_BUILTIN_VEC_SIGNEXT): Add overloaded argument definitions.
        * config/rs6000/vsx.md (vsx_sign_extend_v2di_v1ti): Add define_insn.
        (vsignextend_v2di_v1ti, vsignextend_qi_<mode>, vsignextend_hi_<mode>,
        vsignextend_si_v2di)[VIlong]: Add define_expand.
        Make define_insn vsx_sign_extend_si_v2di visible.
        * doc/extend.texi:  Add documentation for the vec_signexti,
        vec_signextll builtins and vec_signextq.

gcc/testsuite/ChangeLog

        * gcc.target/powerpc/int_128bit-runnable.c (extsd2q): Update expected
        count.
        Add tests for vec_signextq.
        * gcc.target/powerpc/p9-sign_extend-runnable.c:  New test case.


Looking at the GCC 11 tree it looks like I did backport and commit it there as
well:

commit 88b66b376844fe7c537ab229250a41a54e706eaf
Author: Carl Love <c...@us.ibm.com>
Date:   Tue Jun 15 11:37:31 2021 -0500

    RS6000 Add 128-bit Binary Integer sign extend operations

    This patch adds the 128-bit sign extension instruction support and
    corresponding builtin support.

    RS6000 Add 128-bit Binary Integer sign extend operations

    2021-06-08  Carl Love  <c...@us.ibm.com>

    gcc/ChangeLog

            * config/rs6000/altivec.h (vec_signextll, vec_signexti,
vec_signext\
q):
            Add define for new builtins.
            * config/rs6000/altivec.md(altivec_vreveti2): Add define_expand.
            * config/rs6000/rs6000-builtin.def (VSIGNEXTI, VSIGNEXTLL):  Add
            overloaded builtin definitions.
            (VSIGNEXTSB2W, VSIGNEXTSH2W, VSIGNEXTSB2D,
VSIGNEXTSH2D,VSIGNEXTSW2\
D,
            VSIGNEXTSD2Q):  Add builtin expansions.
            (SIGNEXT): Add P10 overload definition.
            * config/rs6000/rs6000-call.c (P9V_BUILTIN_VEC_VSIGNEXTI,
            P9V_BUILTIN_VEC_VSIGNEXTLL, P10_BUILTIN_VEC_SIGNEXT): Add
            overloaded argument definitions.
            * config/rs6000/vsx.md (vsx_sign_extend_v2di_v1ti): Add
define_insn\
.
            (vsignextend_v2di_v1ti, vsignextend_qi_<mode>,
vsignextend_hi_<mode\
>,
            vsignextend_si_v2di)[VIlong]: Add define_expand.
            Make define_insn vsx_sign_extend_si_v2di visible.
            * doc/extend.texi:  Add documentation for the vec_signexti,
            vec_signextll builtins and vec_signextq.

    gcc/testsuite/ChangeLog

            * gcc.target/powerpc/int_128bit-runnable.c (extsd2q): Update
expect\
ed
            count.
            Add tests for vec_signextq.
            * gcc.target/powerpc/p9-sign_extend-runnable.c:  New test case.


Probably should have fixed the commit log date. 

So, it looks to me like this has been done and the issue should be closed.

Reply via email to