lima/gp: Support exp2 and log2
log2 is tricky because there cannot be a move between complex1 and postlog2. We can't guarantee that scheduling complex1 will succeed when we schedule postlog2, so we try to schedule complex1 and if it fails we back out by rewriting the postlog2 as a move and introducing a new postlog2 so that we can try again later. Signed-off-by: Connor Abbott <cwabbott0@gmail.com> Acked-by: Qiang Yu <yuq825@gmail.com>
This commit is contained in:
@@ -118,6 +118,8 @@ static int nir_to_gpir_opcodes[nir_num_opcodes] = {
|
||||
[nir_op_fmax] = gpir_op_max,
|
||||
[nir_op_frcp] = gpir_op_rcp,
|
||||
[nir_op_frsq] = gpir_op_rsqrt,
|
||||
[nir_op_fexp2] = gpir_op_exp2,
|
||||
[nir_op_flog2] = gpir_op_log2,
|
||||
[nir_op_slt] = gpir_op_lt,
|
||||
[nir_op_sge] = gpir_op_ge,
|
||||
[nir_op_fcsel] = gpir_op_select,
|
||||
|
Reference in New Issue
Block a user