diff options
author | Jakub Jelinek <jakub@redhat.com> | 2024-01-19 10:00:16 +0100 |
---|---|---|
committer | Jakub Jelinek <jakub@redhat.com> | 2024-01-19 10:00:16 +0100 |
commit | dcd5601c2b7298155c9a8e1bfb93ee8e952eca0b (patch) | |
tree | 61b5f5c71eab390729d15e80326968f8de03db18 /gcc/cp/error.cc | |
parent | 56778b69ce558bb7e3ab7c561ee4ee48ac20263b (diff) | |
download | gcc-dcd5601c2b7298155c9a8e1bfb93ee8e952eca0b.zip gcc-dcd5601c2b7298155c9a8e1bfb93ee8e952eca0b.tar.gz gcc-dcd5601c2b7298155c9a8e1bfb93ee8e952eca0b.tar.bz2 |
sccvn: Don't use SCALAR_INT_TYPE_MODE on BLKmode BITINT_TYPEs [PR113459]
sccvn uses GET_MODE_SIZE (SCALAR_INT_TYPE_MODE (type)) for INTEGER_TYPEs,
most likely because that is what native_{interpret,encode}_int used.
This obviously doesn't work for larger BITINT_TYPEs which have BLKmode
and the above ICEs on those. native_{interpret,encode}_int checks whether
the BITINT_TYPE is medium/large/huge (i.e. an array of 2+ ABI limbs)
and uses TYPE_SIZE_UNIT for that case, otherwise SCALAR_INT_TYPE_MODE like
for the INTEGER_TYPE case.
The following patch instead just uses SCALAR_INT_TYPE_MODE for non-BLKmode
TYPE_MODE and TYPE_SIZE_UNIT otherwise.
2024-01-19 Jakub Jelinek <jakub@redhat.com>
PR tree-optimization/113459
* tree-ssa-sccvn.cc (vn_walk_cb_data::push_partial_def): Use
TREE_INT_CST_LOW of TYPE_SIZE_UNIT rather than GET_MODE_SIZE
of SCALAR_INT_TYPE_MODE if type has BLKmode.
(vn_reference_lookup_3): Likewise. Formatting fix.
* gcc.dg/bitint-73.c: New test.
Diffstat (limited to 'gcc/cp/error.cc')
0 files changed, 0 insertions, 0 deletions