ir validation assert on valid GLSL
Submitted by Dave Airlie
Assigned to mes..@..op.org
Link to original bug (#102021)
Description
Created attachment 133219 test to demonstrate error.
I've written a cut down test that shows a problem virgl hits.
It triggers an assert in the validation that the ir->type and ir->operands[0]->type for an abs op are the same and they aren't.
temp0[1].x = float(inversesqrt( abs(temp0[0]).x)); temp0[1].y = float(inversesqrt( abs(temp0[0]).y));
is the construct that the compiler squashes incorrectly.
Not sure what pass is responsible for this yet.
Attachment 133219, "test to demonstrate error.":
glsl-test.shader_test
Version: git