Age | Commit message (Collapse) | Author |
|
Split hw vs pipe states creation handling as hw states group doesn't
match pipe state group exactly. Right now be dumb about that and
rebuild all hw states on each draw call. More optimization on that
side coming.
Signed-off-by: Jerome Glisse <jglisse@redhat.com>
|
|
|
|
The type signatures were completely backwards.
|
|
|
|
Both 1.10 and 1.30 variants.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
There's no need to use an ir_expression; we have a handy C function.
|
|
|
|
|
|
This shouldn't be required since dot is only defined for floating point
types, even in GLSL 4.0.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
These builtin functions are represented by ir_expression_operations, so
we can just create one of those and ask for its value.
|
|
These always return zero (the derivative of a constant).
|
|
|
|
|
|
|
|
|
|
This conveniently creates a zero value of whatever type you want.
|
|
Fixes:
glsl-arb-fragment-coord-conventions-define
|
|
Fixes:
glsl-arb-fragment-coord-conventions
|
|
The rest cannot be handled until built-in variables (i.e.,
gl_FragCoord) can be redeclared to add qualifiers.
|
|
|
|
Fixes:
glsl1-varying read but not written
glsl1-varying var mismatch
|
|
This fixes an assertion failure in ir_to_mesa, and the varying won't
take up varying space.
|
|
This is now consistent with other usage of flex/bison througout mesa,
(which is that these generated files are added to source control so
that the build system does not require external tools like flex/bison
for non-developers).
|