need to write HDC code

This is a new unified set of opcodes for memory access loosely patterned
after the new LSC-style data port messages introduced on Alchemist GPUs.

Rather than creating an opcode for every type of memory access, it has
only three opcodes: load, store, and atomic.  It has various sources to
indicate the rest:

- Binding type (raw pointer, pointer to surface state, or BT index)
- Address size (A64, A32, A16)
- Data size (bit size, number of components)
- Opcode (atomic opcode, or LOAD/STORE vs. LOAD_CMASK/STORE_CMASK)
- Mode (typed vs. untyped vs. shared-local vs. scratch)
- Address (and its dimensionality)
- Data (0 for loads, 1 for stores, 2 for atomics)
- Whether we want block access

Nobody uses the VEC4_OPCODEs in the FS backend.

There are a number of places where getting a constant source returned as
an actual immediate value is convenient.  Typically, most of those are
set up to deal with 32-bit constants.  64-bit immediates have too many
restrictions, and even 8 or 16-bit immediates may need expanding.

Rather than asserting that the operand is 32-bit though, and making each
caller choose, we can just only return IMM for 32-bit values, and make
it fall back to get_nir_src for the others, so it's safe to call at any
bit-size.

David Heidelberg authored 1 year ago and Marge Bot committed 1 year ago

This commit introduces multiple changes:
  1. Now we check for mainline artifacts only when NOT running on
     the mainline branch
  2. if we run on the fork and get 404-like error, it doesn't retry.

Reviewed-by: Guilherme Gallo <guilherme.gallo@collabora.com>
Signed-off-by: David Heidelberg <david.heidelberg@collabora.com>
Part-of: <mesa/mesa!22386>