[Bug testsuite/107338] new test case gcc.dg/vect/vect-bitfield-read-7.c in r13-3413-ge10ca9544632db fails

["cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>]

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

--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Kewen Lin <linkw@gcc.gnu.org>:

https://gcc.gnu.org/g:958014f369c8817184af110f8eb2c433a712fd0a

commit r13-3474-g958014f369c8817184af110f8eb2c433a712fd0a
Author: Kewen Lin <linkw@linux.ibm.com>
Date:   Tue Oct 25 00:18:08 2022 -0500

    vect: Fix wrong shift_n after widening on BE [PR107338]

    As PR107338 shows, with the use of widening loads, the
    container_type can become a wider type, it causes us to
    get wrong shift_n since the BIT_FIELD_REF offset actually
    becomes bigger on BE.  Taking the case in PR107338 as
    example, at the beginning the container type is short and
    BIT_FIELD_REF offset is 8 and size is 4, with unpacking to
    wider type int, the high 16 bits are zero, by viewing it
    as type int, its offset actually becomes to 24.  So the
    shift_n should be 4 (32 - 24 - 4) instead of 20 (32 - 8
    - 4).

    I noticed that if we move shift_n calculation early
    before the adjustments for widening loads (container type
    change), it's based on all the stuffs of the original
    container, the shfit_n calculated there is exactly what
    we want, it can be independent of widening.  Besides, I
    add prec adjustment together with the current adjustments
    for widening loads, although prec's subsequent uses don't
    require this change for now, since the container type gets
    changed, we should keep the corresponding prec consistent.

            PR tree-optimization/107338

    gcc/ChangeLog:

            * tree-vect-patterns.cc (vect_recog_bitfield_ref_pattern): Move
            shfit_n calculation before the adjustments for widening loads.