tree 41416c23fd38e7e2eea7094d4c217c3588e0dea2
parent 739ab4cf11f69d9a5e76b56e9f0d312ffcd0dd5c
author Nikita Popov <npopov@redhat.com> 1713422652 +0900
committer Copybara-Service <copybara-worker@google.com> 1713423131 -0700

[IR][PatternMatch] Only accept poison in getSplatValue() (#89159)

In #88217 a large set of matchers was changed to only accept poison
values in splats, but not undef values. This is because we now use
poison for non-demanded vector elements, and allowing undef can cause
correctness issues.

This patch covers the remaining matchers by changing the AllowUndef
parameter of getSplatValue() to AllowPoison instead. We also carry out
corresponding renames in matchers.

As a followup, we may want to change the default for things like m_APInt
to m_APIntAllowPoison (as this is much less risky when only allowing
poison), but this change doesn't do that.

There is one caveat here: We have a single place
(X86FixupVectorConstants) which does require handling of vector splats
with undefs. This is because this works on backend constant pool
entries, which currently still use undef instead of poison for
non-demanded elements (because SDAG as a whole does not have an explicit
poison representation). As it's just the single use, I've open-coded a
getSplatValueAllowUndef() helper there, to discourage use in any other
places.

GitOrigin-RevId: 1baa3850656382d1d549a13f8a716ef5dc886eb8