| Age | Commit message (Collapse) | Author |
|---|
|
|
|
This fixes invalid array indexing when baseLevel == MAX_TEXTURE_LEVELS.
See bug 25528.
|
|
The util_format_layout name was unfortunate and there
are as been a lot of confusion due to this. Hopefully
this will shed some light on what it was meant for.
Bottom line is: do not rely on these values unless
you're automatically code generating pixel
packing/unpacking routines.
Suggestions for better names than util_format_layout
are welcome!
|
|
|
|
|
|
|
|
If the active texture unit on entry to mipmap generation is not zero, bind the
texture to unit zero.
Fixes bug #24219.
|
|
The assertion is that the correct read type to be using is the native
type of the underlying read renderbuffer. For some fallback paths, this
may be worse than GL_RGBA/GL_UNSIGNED_BYTE for reads today, but it gets
all drivers the expected GL_BGRA/GL_UNSIGNED_BYTE for ARGB8888 or
GL_BGR//GL_UNSIGNED_SHORT_5_6_5_REV for rgb565 with no work.
This fixes the intel (and other) DRI drivers to report read formats that
should hit blit PBO readpixels paths.
|
|
_mesa_LightModeli calls _mesa_LightModeliv, which uses the
params argument as an array.
|
|
_mesa_Fogf calls _mesa_Fogfv, which uses the params argument
as an array.
|
|
_mesa_TexParameteri calls set_tex_parameteri, which uses the
params argument as an array.
|
|
Passes piglit pbo-read-argb8888, and doesn't otherwise regress quick.tests.
|
|
_mesa_Fogi calls _mesa_Fogfv, which uses the params argument
as an array.
|
|
_mesa_TexParameteri calls set_tex_parameterf, which uses the
params argument as an array.
|
|
_mesa_TexParameterfv calls set_tex_parameteri, which uses the
params argument as an array.
|
|
Fixes bug 25525.
Plus, the GL_NV_vertex_program evaluators alias and override the
convential evaluator maps, so set their state after the conventional
maps.
|
|
|
|
|
|
all code in gallium should use boolean not bool
|
|
|
|
In particular, gcc man page warns that
union a_union {
int i;
double d;
};
int f() {
double d = 3.0;
return ((union a_union *) &d)->i;
}
"might" not be ok (why not?), even though it doesn't seem to generate
any warnings. Hence don't use this and do the extra step to actually use
assignment to get the values in/out of the union.
This changes parts of 3456f9149b3009fcfce80054759d05883d3c4ee5.
|
|
The ureg and/or tgsi-simplification work introduced some inconsistencies
between the ureg and traditional TGSI construction code.
Now the tgsi_instruction::NrTokens field is consistant and the
tgsi_header::BodySize field isn't off by one.
Fixes bug 25455.
|
|
|
|
|
|
|
|
|
|
and use it in cubemap instruction sequence for testing
|
|
|
|
use it in tex cube instruction sequence
|
|
looks kinda hackish, should rethink later
|
|
|
|
|
|
remember the dst register which is used for cond updates
when it's time to use the cond codes issue a separate PRED instruction
|
|
seems assemble_LOGIC was meant for non-condition-code instructions
so execute in for all components as previously
|
|
|
|
|
|
Not sure how vmw_screen.c could build at all though...
|
|
|
|
Conflicts:
src/mesa/drivers/dri/r600/r700_assembler.c
src/mesa/main/version.h
|
|
|
|
|
|
Silences uninitialized variable warning.
|
|
|
|
makes testing other things easier - does not hang the card
TODO: enable TEX dependency tracking in vertex programs
|
|
First time around render targets are not enabled yet (done in
r700SendRenderTargetState) so blend state is not emitted for any targets.
Affects first glClear in some mesa tests.
As a quick fix reorder state emit so that target is set first
|
|
|
|
Silences uninitialized variable compiler warning.
|
|
Also modify the Makefile to use the correct version for the tarballs.
|
|
Conflicts:
progs/demos/projtex.c
progs/xdemos/glxinfo.c
src/mesa/main/version.h
To fix the confilicts in projtex.c and glxinfo.c I just took the code from
mesa_7_6_branch. The conflicts seem to have occured from cherry-picks from
mesa_7_7_branch to mesa_7_6_branch followed by commmits just to
mesa_7_6_branch.
|
|
buffers."
This reverts commit 4598942b1b88a2a7d5af7febae7e79eedf00e385.
XRGB8888 doesn't work as intended. Revert this for now, and we'll revisit it
for 7.8 or something.
|
