explow: Fix ICE caused by plus_constant [PR94002]
authorJakub Jelinek <jakub@redhat.com>
Tue, 3 Mar 2020 09:42:34 +0000 (10:42 +0100)
committerJakub Jelinek <jakub@redhat.com>
Tue, 3 Mar 2020 09:42:34 +0000 (10:42 +0100)
commit0ab503d34f2a8c22262ceefea6c882ae2ff75230
tree6acca675299dafaf4c74ae6ebe92130898c90edf
parent02ae0e08a93f41022d1584054cf6111548c0d954
explow: Fix ICE caused by plus_constant [PR94002]

The following testcase ICEs in cross to riscv64-linux.  The problem is
that we have a DImode integral constant (that doesn't fit into SImode),
which is pushed into a constant pool and later access just the first half of
it using a MEM.  When plus_constant is called on such a MEM, if the constant
has mode, we verify the mode, but if it doesn't, we don't and ICE later on
when we think the CONST_INT is a valid SImode constant.

2020-03-03  Jakub Jelinek  <jakub@redhat.com>

PR rtl-optimization/94002
* explow.c (plus_constant): Punt if cst has VOIDmode and
get_pool_mode is different from mode.

* gcc.dg/pr94002.c: New test.
gcc/ChangeLog
gcc/explow.c
gcc/testsuite/ChangeLog
gcc/testsuite/gcc.dg/pr94002.c [new file with mode: 0644]