| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| | |
Conflicts:
src/gallium/state_trackers/xorg/xorg_xv.c
src/mesa/drivers/dri/intel/intel_span.c
|
| |\ |
|
| | | |
|
| |\| |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If a register was only being used as a destination (as will happen when
generated condition-codes) we missed its use. So we'd errantly return
a register index that was really in-use, not free.
Fixes bug 25579.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
For some cases, _mesa_GetIntegerv reads up to params[15].
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
_mesa_TexGend calls _mesa_TexGenfv, which uses the params argument
as an array.
|
| | |
| | |
| | |
| | |
| | | |
_mesa_Lighti calls _mesa_Lightiv, which uses the params argument
as an array.
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
_mesa_PointParameteri calls _mesa_PointParameterfv, which uses the
params argument as an array.
|
| | |
| | |
| | |
| | |
| | | |
_mesa_PointParameterf calls _mesa_PointParameterfv, which uses the
params argument as an array.
|
| | |
| | |
| | |
| | |
| | | |
_mesa_LightModelf calls _mesa_LightModelfv, which uses the
params argument as an array.
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
This fixes invalid array indexing when baseLevel == MAX_TEXTURE_LEVELS.
See bug 25528.
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
_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.
|
| | |
| | |
| | |
| | |
| | | |
_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.
|
| | |
| | |
| | |
| | |
| | | |
Now that XRGB is supported, we don't need to hack around cases of an RGBA
format buffer with an internal format of GL_RGB.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
It turns out that 965 and friends cannot actually render to an xRGB
surfaces. Instead, the surface has to be RGBA with writes to alpha
disabled and the blend function modified to always use 1.0 for
destination alpha.
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
This is really for MESA_FORMAT_XRGB8888. Clearly spantmp2.h needs some
re-work. Any volunteers?
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
remove
|
| | |
| | |
| | |
| | |
| | | |
Since the texformat branch merge, the value of intel_renderbuffer::texformat
is just a copy of gl_renderbuffer::Format.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Back when we were flushing the entire batch at BindFramebuffer, the kernel
would notice the domain transition when someone went to texture from it and
flush for us. We no longer do the batch flushing every time, so we get to
do aggressive flushing until we move batchbuffer handling to libdrm.
Fixes piglit fbo-flushing. Bug #25377. No noticeable performance loss
on cairo-gl (so this is better than batch flushing).
|
| | |
| | |
| | |
| | |
| | | |
Commit cd6b8dd9e82fedc55d033131fbc0f8ee950567c8 deleted
src/mesa/state_tracker/st_cb_get.c.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| | |
| | |
| | |
| | | |
Passes piglit pbo-read-argb8888, and doesn't otherwise regress quick.tests.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The swrast pipeline shouldn't have any problem with all the frag and vert
textures being bound at the same time. Note that this may result in
DRI drivers that don't set this limit having an improbable return
(fragment + vertex < combined), but it seems like it shouldn't cause
problems for apps.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The MaxCombinedTextureImageUnits is the total number of samplers that can
be bound between vertex, geometry, and fragment, not 0. This should report
the correct value on 965 now. Other DRI drivers may also need updating if
their MaxVertexTextureImageUnits != 0 (for example, if using the sw vertex
pipeline).
It's not clear to me if there's going to be a valid value for this
limit other than MaxTextureImageUnits + MaxVertexTextureImageUnits (+
MaxGeometryTextureImageUnits eventually). If not, then we should probably
just move this into the core at Get time.
Bug #25518 (wine regression). Fixes piglit vp-combined-image-units.
|
| | |
| | |
| | |
| | | |
complex built-in shader instructions.
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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.
|
| | | |
| | | |
| | | |
| | | | |
use unions instead of pointer casts.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
use pointer to union instead of void pointer.
gcc complained a lot, depending what the pointer originally actually was.
Looks like it's in fact maybe legal to cast for instance uint pointers to
union pointers as long as union contains a uint type, hence use this with some
callers, other just use union util_color in the first place.
|