diff options
author | Jakub Jelinek <jakub@redhat.com> | 2024-12-28 15:42:56 +0100 |
---|---|---|
committer | Jakub Jelinek <jakub@gcc.gnu.org> | 2024-12-28 15:42:56 +0100 |
commit | 65c8fd7b017482c6d6bd0c7a7c6e296f016e38d0 (patch) | |
tree | 5c9356c9a68f8e99b0622b25b24dd50b15b38e86 /gcc/tree-ssa-loop-manip.h | |
parent | a326ecf5411897e975fb24696d3267bbe496627c (diff) | |
download | gcc-65c8fd7b017482c6d6bd0c7a7c6e296f016e38d0.zip gcc-65c8fd7b017482c6d6bd0c7a7c6e296f016e38d0.tar.gz gcc-65c8fd7b017482c6d6bd0c7a7c6e296f016e38d0.tar.bz2 |
gimple-fold: Fix up fold_array_ctor_reference RAW_DATA_CST handling [PR118207]
The following testcases ICE because fold_array_ctor_reference in the
RAW_DATA_CST handling just return build_int_cst without actually checking
that if type is non-NULL, TREE_TYPE (val) is uselessly convertible to it.
By falling through the code after it without *suboff += we get everything
we need, the two if conditionals will never be true (we've already
checked that size == BITS_PER_UNIT and so can't be 0, and val will be
INTEGER_CST), but it will do the important fold_ctor_reference call
which will deal with type incompatibilities.
2024-12-28 Jakub Jelinek <jakub@redhat.com>
PR tree-optimization/118207
* gimple-fold.cc (fold_array_ctor_reference): For RAW_DATA_CST,
just set val to build_int_cst and fall through to the normal
element handling code instead of returning build_int_cst right away.
* gcc.dg/pr118207.c: New test.
Diffstat (limited to 'gcc/tree-ssa-loop-manip.h')
0 files changed, 0 insertions, 0 deletions