aboutsummaryrefslogtreecommitdiff
path: root/gcc/tree-ssa-loop-niter.c
diff options
context:
space:
mode:
authorJakub Jelinek <jakub@redhat.com>2020-04-02 12:57:11 +0200
committerJakub Jelinek <jakub@redhat.com>2020-04-02 12:57:11 +0200
commitdf562b12d90699c20923f91df48eed08ebcb572e (patch)
tree7c0675c7f0d3bdbe237ca58bf2d53ad52bba9a78 /gcc/tree-ssa-loop-niter.c
parent66e327517b10a19690a470c8dccfa363ba061022 (diff)
downloadgcc-df562b12d90699c20923f91df48eed08ebcb572e.zip
gcc-df562b12d90699c20923f91df48eed08ebcb572e.tar.gz
gcc-df562b12d90699c20923f91df48eed08ebcb572e.tar.bz2
aarch64: Fix ICE due to aarch64_gen_compare_reg_maybe_ze [PR94435]
The following testcase ICEs, because aarch64_gen_compare_reg_maybe_ze emits invalid RTL. For y_mode [QH]Imode it expects y to be of that mode (or CONST_INT that fits into that mode) and x being SImode; for non-CONST_INT y it zero extends y into SImode and compares that against x, for CONST_INT y it zero extends y into SImode. The problem is that when the zero extended constant isn't usable directly, it forces it into a REG, but with y_mode mode, and then compares against y. That is wrong, because it should force it into a SImode REG and compare that way. 2020-04-02 Jakub Jelinek <jakub@redhat.com> PR target/94435 * config/aarch64/aarch64.c (aarch64_gen_compare_reg_maybe_ze): For y_mode E_[QH]Imode and y being a CONST_INT, change y_mode to SImode. * gcc.target/aarch64/pr94435.c: New test.
Diffstat (limited to 'gcc/tree-ssa-loop-niter.c')
0 files changed, 0 insertions, 0 deletions