i965/vs: Abort on unsupported opcodes rather than failing.
Final code generation should never fail. This is a bug, and there should be no user-triggerable cases where this could occur. Also, we're not going to have a fail() method after the split. Reviewed-by: Eric Anholt <eric@anholt.net> Reviewed-by: Anuj Phogat <anuj.phogat@gmail.com>
This commit is contained in:
@@ -641,11 +641,12 @@ vec4_visitor::generate_vs_instruction(vec4_instruction *instruction,
|
||||
|
||||
default:
|
||||
if (inst->opcode < (int) ARRAY_SIZE(opcode_descs)) {
|
||||
fail("unsupported opcode in `%s' in VS\n",
|
||||
opcode_descs[inst->opcode].name);
|
||||
_mesa_problem(ctx, "Unsupported opcode in `%s' in VS\n",
|
||||
opcode_descs[inst->opcode].name);
|
||||
} else {
|
||||
fail("Unsupported opcode %d in VS", inst->opcode);
|
||||
_mesa_problem(ctx, "Unsupported opcode %d in VS", inst->opcode);
|
||||
}
|
||||
abort();
|
||||
}
|
||||
}
|
||||
|
||||
|
||||
Reference in New Issue
Block a user