diff options
author | Jakub Jelinek <jakub@redhat.com> | 2020-10-13 19:13:26 +0200 |
---|---|---|
committer | Jakub Jelinek <jakub@redhat.com> | 2020-10-13 19:13:26 +0200 |
commit | f76949cee9560d04d5417481dbcda5ca089c9ebc (patch) | |
tree | ea08e15479dd07b8d8fc78dd9c1f8ed4b36fc985 /lto-plugin | |
parent | 0e0beddd7fb4c0d2157c7f0c7d3f39e9533bb323 (diff) | |
download | gcc-f76949cee9560d04d5417481dbcda5ca089c9ebc.zip gcc-f76949cee9560d04d5417481dbcda5ca089c9ebc.tar.gz gcc-f76949cee9560d04d5417481dbcda5ca089c9ebc.tar.bz2 |
combine: Fix up simplify_shift_const_1 for nested ROTATEs [PR97386]
The following testcases are miscompiled (the first one since my improvements
to rotate discovery on GIMPLE, the other one for many years) because
combiner optimizes nested ROTATEs with narrowing SUBREG in between (i.e.
the outer rotate is performed in shorter precision than the inner one) to
just one ROTATE of the rotated constant. While that (under certain
conditions) can work for shifts, it can't work for rotates where we can only
do that with rotates of the same precision.
2020-10-13 Jakub Jelinek <jakub@redhat.com>
PR rtl-optimization/97386
* combine.c (simplify_shift_const_1): Don't optimize nested ROTATEs if
they have different modes.
* gcc.c-torture/execute/pr97386-1.c: New test.
* gcc.c-torture/execute/pr97386-2.c: New test.
Diffstat (limited to 'lto-plugin')
0 files changed, 0 insertions, 0 deletions