Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions g3doc/quick_reference.md
Original file line number Diff line number Diff line change
Expand Up @@ -1928,16 +1928,16 @@ their operands into independently processed 128-bit *blocks*.

All other ops in this section are only available if `HWY_TARGET != HWY_SCALAR`:

* `V`: `{u,i}` \
* `V`, `VI`: `{u,i}` \
<code>VI **TableLookupBytes**(V bytes, VI indices)</code>: returns
`bytes[indices[i]]`. Uses byte lanes regardless of the actual vector types.
Results are implementation-defined if `indices[i] < 0` or `indices[i] >=
HWY_MIN(Lanes(DFromV<V>()), 16)`. `VI` are integers, possibly of a different
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about something like "VI are normal vectors with integer lane type possibly differing from the lanes of V. Note that TableLookupLanes has an unspecified, potentially non-vector type type for the indices."?

type than those in `V`. The number of lanes in `V` and `VI` may differ, e.g.
a full-length table vector loaded via `LoadDup128`, plus partial vector `VI`
of 4-bit indices.
type than those in `V` and are loaded uses the standard load instructions.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

loading using?

The number of lanes in `V` and `VI` may differ, e.g. a full-length table vector
loaded via `LoadDup128`, plus partial vector `VI` of 4-bit indices.

* `V`: `{u,i}` \
* `V`, `VI`: `{u,i}` \
<code>VI **TableLookupBytesOr0**(V bytes, VI indices)</code>: returns
`bytes[indices[i]]`, or 0 if `indices[i] & 0x80`. Uses byte lanes regardless
of the actual vector types. Results are implementation-defined for
Expand Down