ir3: Use CAN_REORDER instead of NON_WRITEABLE
CAN_REORDER takes volatile into account, and is closer to what we
actually require to use texture instructions, which is that we can
arbitrarily reorder loads.
Fixes: aa93896
("freedreno/ir3: adjust condition for when to use ldib")
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/15114>
This commit is contained in:
parent
95fabff8de
commit
e1c4c2ac60
|
@ -1396,7 +1396,7 @@ emit_intrinsic_load_image(struct ir3_context *ctx, nir_intrinsic_instr *intr,
|
|||
/* If the image can be written, must use LDIB to retrieve data, rather than
|
||||
* through ISAM (which uses the texture cache and won't get previous writes).
|
||||
*/
|
||||
if (!(nir_intrinsic_access(intr) & ACCESS_NON_WRITEABLE) && ctx->compiler->gen >= 5) {
|
||||
if (!(nir_intrinsic_access(intr) & ACCESS_CAN_REORDER) && ctx->compiler->gen >= 5) {
|
||||
ctx->funcs->emit_intrinsic_load_image(ctx, intr, dst);
|
||||
return;
|
||||
}
|
||||
|
|
Loading…
Reference in New Issue