diff options
| author | Andrew Pinski <quic_apinski@quicinc.com> | 2025-02-20 16:09:05 -0800 |
|---|---|---|
| committer | Andrew Pinski <quic_apinski@quicinc.com> | 2025-04-18 09:13:04 -0700 |
| commit | 94f275432f7ea4781ec7c05fa9d1d81ef6cb3fc1 (patch) | |
| tree | 76c708a854f92db998702fa81c15e516c6985360 /libjava/gnu/java/security/ber | |
| parent | baf6ad5dad55a7aa1e75d4ccadc05347b4506a1f (diff) | |
| download | gcc-94f275432f7ea4781ec7c05fa9d1d81ef6cb3fc1.zip gcc-94f275432f7ea4781ec7c05fa9d1d81ef6cb3fc1.tar.gz gcc-94f275432f7ea4781ec7c05fa9d1d81ef6cb3fc1.tar.bz2 | |
gimple-fold: Improve optimize_memcpy_to_memset to handle STRING_CST [PR78408]
While looking into PR 118947, I noticed that optimize_memcpy_to_memset didn't
handle STRING_CST which are also used for a memset of 0 but for char arrays.
This fixes that and improves optimize_memcpy_to_memset to handle that case.
This fixes part of PR 118947 but not the whole thing; we still need to skip over
vdefs in some cases.
Boostrapped and tested on x86_64-linux-gnu.
PR tree-optimization/78408
PR tree-optimization/118947
gcc/ChangeLog:
* gimple-fold.cc (optimize_memcpy_to_memset): Handle STRING_CST case too.
gcc/testsuite/ChangeLog:
* gcc.dg/pr78408-3.c: New test.
Signed-off-by: Andrew Pinski <quic_apinski@quicinc.com>
Diffstat (limited to 'libjava/gnu/java/security/ber')
0 files changed, 0 insertions, 0 deletions