[Bug tree-optimization/116081] [15 Regression] Different code generation in the vectorizer with a typedef vs not

[cvs-commit at gcc dot gnu.org via Gcc-bugs]

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

--- Comment #8 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Biener <rgue...@gcc.gnu.org>:

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

commit r15-2311-g3f578dbac726d47b043b82606c47e5676c5d6a14
Author: Richard Biener <rguent...@suse.de>
Date:   Thu Jul 25 12:46:30 2024 +0200

    tree-optimization/116081 - typedef vs. non-typedef in vectorization

    The following fixes the code generation difference when using
    a typedef for the scalar type.  The issue is using a pointer
    equality test for an INTEGER_CST which fails when the types
    are different variants.

            PR tree-optimization/116081
            * tree-vect-loop.cc (get_initial_defs_for_reduction):
            Use operand_equal_p for comparing the element with the
            neutral op.