aboutsummaryrefslogtreecommitdiff
path: root/gcc/gcov-io.cc
diff options
context:
space:
mode:
authorJakub Jelinek <jakub@redhat.com>2022-03-30 10:21:16 +0200
committerJakub Jelinek <jakub@redhat.com>2022-03-30 10:21:16 +0200
commit387e818cda0ffde86f624228c3da1ab28f453685 (patch)
tree8df9a9b6da26884063bede81345849558b8c9633 /gcc/gcov-io.cc
parent410f39f56c14b195f066b9a18a3c6e8ffa03f848 (diff)
downloadgcc-387e818cda0ffde86f624228c3da1ab28f453685.zip
gcc-387e818cda0ffde86f624228c3da1ab28f453685.tar.gz
gcc-387e818cda0ffde86f624228c3da1ab28f453685.tar.bz2
store-merging: Avoid ICEs on roughly ~0ULL/8 sized stores [PR105094]
On the following testcase on 64-bit targets, store-merging sees a MEM_REF store from {} ctor with "negative" bitsize where bitoff + bitsize wraps around to very small end offset. This later confuses the code so that it allocates just a few bytes of memory but fills in huge amounts of it. Later on there is a param_store_merging_max_size size check but due to the wrap-around we pass that. The following patch punts on such large bitsizes. 2022-03-30 Jakub Jelinek <jakub@redhat.com> PR tree-optimization/105094 * gimple-ssa-store-merging.cc (mem_valid_for_store_merging): Punt if bitsize <= 0 rather than just == 0. * gcc.dg/pr105094.c: New test.
Diffstat (limited to 'gcc/gcov-io.cc')
0 files changed, 0 insertions, 0 deletions