| Age | Commit message (Collapse) | Author |
|---|
|
This is used to wrap user-space data in a pipe buffer object to allow more
uniform treatment of various things. For example, wrapping client-side
vertex arrays so they look like VBOs.
|
|
|
|
|
|
|
|
ignored for now
|
|
|
|
texture and level!=0)
|
|
|
|
|
|
tgsi_translate_mesa_program().
|
|
|
|
|
|
|
|
Previously, output[0] was always Z and output[1] was color. Now output[0]
will be color if Z is not written.
In shade_quad() use the semantic info to determine which quantity is in
which output slot.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
fragment shader writes Z.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Unfortunately, the generated fragment shader code is effectively unusable until
it handles quad->mask.
|
|
structure so allocate a private copy of it.
|
|
location.
|
|
the clipping code.
(really done by Keith)
|
|
in the state functions.
|
|
|
|
|
|
|
|
These correspond to the NV and ARB-style fragment program KIL instructions.
The former is really supposed to examine the NV condition codes but Mesa's
GLSL compiler always emits unconditional KIL instructions.
|
|
Still need to handle conditional RET statements...
|
|
|
|
|
|
|
|
|
|
GLSL output variables (such as vertex varyings) can be read (they're not
write-only).
|
|
The glsl/brick.c shader demo runs now.
|
|
Halt program execution when we get to END instruction. The GLSL compiler
puts subroutines after the end instruction so we have to stop before then.
|
|
|
|
|
|
|
|
This, plus expanding all instructions ahead of time, seems to have improved
the performance of program execution by 8x or so.
|
|
works.
|
|
|
