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.
This commit is contained in:
Jakub Jelinek 2022-02-25 18:58:48 +01:00
parent cc187fbca7
commit 3885a122f8
2 changed files with 23 additions and 1 deletions

View File

@ -1519,7 +1519,10 @@
[(set (match_operand:VEC_N 0 "nonimmediate_operand")
(match_operand:VEC_N 1 "any_operand"))]
"VECTOR_MEM_VSX_P (<MODE>mode) && TARGET_ALLOW_MOVMISALIGN"
"")
{
rs6000_emit_move (operands[0], operands[1], <MODE>mode);
DONE;
})
;; Vector shift right in bits. Currently supported ony for shift
;; amounts that can be expressed as byte shifts (divisible by 8).

View File

@ -0,0 +1,19 @@
// PR target/104681
// { dg-do compile }
// { dg-options "-O2" }
void bar ();
struct A {
A (bool) : a(7.0L), b(0) {}
long double a;
long b;
};
struct B {
void foo () { c = bar; }
A c;
};
struct C {
void baz ();
B d;
};
void C::baz () { d.foo (); }