diff options
| author | Jason Ekstrand <jason@jlekstrand.net> | 2021-06-17 10:32:34 -0500 |
|---|---|---|
| committer | Marge Bot <eric+marge@anholt.net> | 2021-06-21 16:46:59 +0000 |
| commit | f00b5a30f5799b5072197ecb92bbcc16877109cd (patch) | |
| tree | de433de6910470f1689095c5667c88162d4625ab /docs/index.rst | |
| parent | ea68d4a676260d9c45dfbe0cb8de8e40869b5523 (diff) | |
nir: Require vectorized ALU ops to be all-or-nothing
Long ago, the semantics of bcsel were such that it took a single boolean
value and selected between whole vectors. These days, it takes a vector
boolean with the assumption that if you want the old behavior you can
just use a .xxxx swizzle. There currently are no opcodes which use a
output_size of 0 but have a scalar or fixed-vector input. Let's
disallow it for now to force us to think through the semantics again if
this ever comes up as something someone actually wants.
Reviewed-by: Connor Abbott <cwabbott0@gmail.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11438>
Diffstat (limited to 'docs/index.rst')
0 files changed, 0 insertions, 0 deletions