| Age | Commit message (Collapse) | Author |
|---|
|
|
|
to slip over the allocated memory for the vb.
pull in sse fixes from gallium-0.1
|
|
to slip over the allocated memory for the vb.
|
|
|
|
|
|
|
|
module.
|
|
|
|
|
|
t_vb_program.c
|
|
|
|
|
|
do the same math as for fixed function pipe, including
user clip planes.
(mostly resurrected from the dead t_vb_arbprogram.c code)
|
|
_mesa_exec_malloc() returns NULL.
(picked from mesa_7_0_branch)
|
|
|
|
|
|
|
|
|
|
|
|
New _mesa_get_fixed_func_vertex_program() function...
|
|
It looks like Windows does not like filenames ending with a dot,
in effect renaming it to 'mms-config'.
|
|
|
|
|
|
|
|
|
|
|
|
We always need to compute the absolute value of the fogcoord if we're
passing it through for per-fragment fog.
|
|
|
|
|
|
are needed.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
ctx->Driver.RasterPos() function.
|
|
|
|
(uniform) is written to. (see bug 12239)
Also, added some assertions to the emit_arg() and emit_dst() functions to
catch this kind of error in the future.
|
|
fix bug#11009
|
|
The code is all in place, but mostly disabled for now:
In t_vp_build.c, write the VERT_RESULT_PSIZE register
In sp_state_derived.c, need to emit vertex point size if drawing points.
In setup_point() use the point size from the vertex.
|
|
|
|
|
|
|
|
The clamping for these values depends on whether we're drawing AA or non-AA
points, lines. Defer clamping until drawing time. Drivers could compute and
keep clamped AA and clamped non-AA values if desired.
|
|
of -I flags.
|
|
|
|
|
|
ctx->Point._Attentuation was computed in wrong place and the VB->Eye coord Z
array wasn't indexed correctly in run_point_stage().
|
