diff options
| author | Jakub Jelinek <jakub@redhat.com> | 2024-01-12 11:22:04 +0100 |
|---|---|---|
| committer | Jakub Jelinek <jakub@redhat.com> | 2024-01-12 11:22:04 +0100 |
| commit | 4c08f0dde4c2a48931a61b84a00d5c16f4b0e291 (patch) | |
| tree | fe9c77935deb9b48b8fa237d9ed5dc82853bd044 /gcc/function.cc | |
| parent | a2d66158541c0923620b044098bf66a73b51c463 (diff) | |
| download | gcc-4c08f0dde4c2a48931a61b84a00d5c16f4b0e291.zip gcc-4c08f0dde4c2a48931a61b84a00d5c16f4b0e291.tar.gz gcc-4c08f0dde4c2a48931a61b84a00d5c16f4b0e291.tar.bz2 | |
sra: Punt for too large _BitInt accesses [PR113330]
This is the case I was talking about in
https://gcc.gnu.org/pipermail/gcc-patches/2024-January/642423.html
and Zdenek kindly found a testcase for it.
We can only create BITINT_TYPE with precision at most 65535, not 65536,
so need to punt if we'd want to create it.
2024-01-12 Jakub Jelinek <jakub@redhat.com>
PR tree-optimization/113330
* tree-sra.cc (create_access): Punt for BITINT_TYPE accesses with
too large size.
* gcc.dg/bitint-69.c: New test.
Diffstat (limited to 'gcc/function.cc')
0 files changed, 0 insertions, 0 deletions