Page MenuHomePhabricator

[ARM] MVE vector of 64bit types

Authored by dmgreen on Jul 8 2019, 2:33 AM.



We need to make sure that we are sensibly dealing with vectors of type v2i64 and v2f64, even if most of the time we cannot generate native operations for them. This mostly adds a lot of testing, plus fixes up a couple of the issues found. And, Or and xor can be legal for v2i64, and shifts combining needs a slight fixup.

Diff Detail


Event Timeline

dmgreen created this revision.Jul 8 2019, 2:33 AM
dmgreen updated this revision to Diff 208352.Jul 8 2019, 3:32 AM

Updates tests

SjoerdMeijer added inline comments.Jul 9 2019, 2:48 AM
337 ↗(On Diff #208352)

Do we need to predicate this on MVE?

dmgreen marked an inline comment as done.Jul 9 2019, 3:05 AM
dmgreen added inline comments.
337 ↗(On Diff #208352)

Yep, we only call this if we have MVEIntegerOps. Neon is handled elsewhere and I think will promote all and/or/xors to v4i32.

SjoerdMeijer accepted this revision.Jul 9 2019, 3:48 AM

looks good to me

337 ↗(On Diff #208352)

Ah, of course, cheers

This revision is now accepted and ready to land.Jul 9 2019, 3:48 AM
This revision was automatically updated to reflect the committed changes.