]> gcc.gnu.org Git - gcc.git/commit
rs6000: Use rs6000_emit_move in movmisalign<mode> expander [PR104681]
authorJakub Jelinek <jakub@redhat.com>
Fri, 25 Feb 2022 17:58:48 +0000 (18:58 +0100)
committerJakub Jelinek <jakub@redhat.com>
Tue, 10 May 2022 08:14:34 +0000 (10:14 +0200)
commitcc7bc8b2ba5adc89e99bc7923cd3e822b7d465cf
tree9293cb9d39dc5297dd296ac72d1f44227b70c2a5
parent1a8b7fb748f95646f314d5dd7a5af48542c3e925
rs6000: Use rs6000_emit_move in movmisalign<mode> expander [PR104681]

The following testcase ICEs, because for some strange reason it decides to use
movmisaligntf during expansion where the destination is MEM and source is
CONST_DOUBLE.  For normal mov<mode> expanders the rs6000 backend uses
rs6000_emit_move to ensure that if one operand is a MEM, the other is a REG
and a few other things, but for movmisalign<mode> nothing enforced this.
The middle-end documents that movmisalign<mode> shouldn't fail, so we can't
force that through predicates or condition on the expander.

2022-02-25  Jakub Jelinek  <jakub@redhat.com>

PR target/104681
* config/rs6000/vector.md (movmisalign<mode>): Use rs6000_emit_move.

* g++.dg/opt/pr104681.C: New test.

(cherry picked from commit 3885a122f817a1b6dca4a84ba9e020d5ab2060af)
gcc/config/rs6000/vector.md
gcc/testsuite/g++.dg/opt/pr104681.C [new file with mode: 0644]
This page took 0.066999 seconds and 6 git commands to generate.