| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
(cherry picked from master, commit cc22620e4b11425997f3bc1fc70f4c88cec22d2e)
|
|
|
|
|
|
|
| |
Add _NEW_PROGRAM_CONSTANTS to _SWRAST_NEW_DERIVED.
This makes sure that we update the fragment shader's constants when state
vars (such as point size) changes.
Fixes the progs/glsl/points.c demo.
|
|
|
|
| |
(cherry picked from master, commit d9617deb008b75f4a605a30408aeb1948139c33e)
|
|
|
|
| |
See comments for details.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The existing implementation was already implemented on software, but relied
on the pipe driver to always support the R16G16B16A16_SNORM format. This
patch eliminates that, without prejudice against a future hardware-only
implementation.
It also avoids some of the short <-> float conversions, and only does a read
transfer of the color buffer on GL_RETURN if absolutely necessary.
|
|
|
|
|
| |
In st_bufferobj_map_range(), set obj->Offset consistently with its
usage elsewhere.
|
|
|
|
| |
(cherry picked from master, commit ef8caec29ae73bb2bbeb48f0578d839ef29348cd)
|
| |
|
|
|
|
| |
(cherry picked from master, commit 19a54d9f1055c366fd77026dd67007a8d5921f58)
|
|
|
|
|
|
| |
It's legal for ARB_vertex_program programs to not write to result.position.
The results are undefined in that case. This assertion was causing us to
abort/exit though.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The recent increase ST_MAX_SHADER_TOKENS to 8K causes stack overflows on
windows.
Failure to allocate is not being propagated to the caller. This is not
a regression since the previous _mesa_malloc result wasn't being
checked as well. Unfortunately it is not easy to fix, as the callers of
these functions do not have failure propagation mechanism either, and
so on. So leaving a just fixme note for now.
|
| |
|
|
|
|
| |
Also, MAX_NV_VERTEX_PROGRAM_PARAMS should be 96, not 128 (or 256).
|
|
|
|
|
|
| |
We were adding references to the input arrays, but failing to drop
them on destruction. This could lead to a 64kb buffer being leaked
each context destruction.
|
|
|
|
|
|
|
|
|
|
| |
1) Pass the correct format when calling update_array in
_mesa_VertexAttribPointerARB.
2) glVertexAttribPointerNV accepts GL_BGRA format too.
3) raise INVALID_VALUE error when format is BGRA and normalized is
false in glVertexAttribPointerARB
(cherry picked from commit 4adb190a162c5ed0684a8616331344caadba4010)
|
| |
|
|
|
|
|
|
|
|
|
|
| |
autoconf had been designating the 8 bit libOSMesa as the default
standalone osmesa, but the Makefile expected it to be linked to libGL.
Fix up the osmesa Makefile so that it allows any of the combinations of
standalone and channel width to be built.
Fixes bug #21980.
(cherry picked from commit 7441dcd90b01df8351026af8bbb50e11bb86071a)
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This prevents the width / height from being clipped to the window size before
the texture is allocated. This matches intelCopyTexImage1D.
This should fix bug #21227
Signed-off-by: Ian Romanick <[email protected]>
(cherry picked from commit 129f311673c99eb912d659023e50bc5f0ef53249)
|
|
|
|
| |
Need a flush here even though the original finish was overkill.
|
| |
|
|
|
|
|
|
|
| |
Need to take the draw buffer's up/down orientation into consideration
when setting the sprite_coord_mode field.
Fixes inverted sprites when drawing into an FBO.
|
|
|
|
|
| |
Stderr of Windows applications without console is not usually
visible.
|
|
|
|
|
| |
Prevents segmentation fault when trying to set the viewport/scissor
after a context/drawable visual mismatch.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
When a vertex shader uses generic vertex attribute 0, but not gl_Vertex,
we need to set attribute[16] to point to attribute[0]. We were setting the
attribute size, but not the pointer.
Fixes crash in glsl/multitex.c when using the VertCoord attribute instead
of gl_Vertex.
|
|
|
|
|
|
|
| |
It's possible to hand a GL_COLOR_INDEX/GL_BITMAP image to glTexImage3D()
which gets converted to RGBA via the glPixelMap tables.
This fixes a failure with piglit/fdo10370 with Gallium.
|
| |
|
| |
|
|
|
|
|
|
| |
The generic_array[] is 16 elements in size, but the loop was doing 32
iterations. The out of bounds array write was clobbering the following
inputs[] array but as luck would have it, that didn't matter.
|
| |
|
|
|
|
| |
See sourceforge bug #2793846.
|
|
|
|
| |
When we render to a depth/stencil texture there are stencil bits.
|
|
|
|
| |
The stride needs to be in texels, not bytes.
|
| |
|
|
|
|
| |
We were passing a GL texture target instead of a pipe_texture_target enum.
|
| |
|
|
|
|
| |
Fixes potential texture object leaks.
|
|
|
|
| |
Fixes segfault in context tear-down when glClear was never called.
|
|
|
|
|
|
|
|
|
| |
gl_array_object encapsulates a set of vertex arrays (see the
GL_APPLE_vertex_array_object extension).
Create a private gl_array_object for drawing the quad for intel_clear_tris()
so we don't have to worry about the user's vertex array state.
This fixes the no-op glClear bug #21638 and removes the need to call
_mesa_PushClientAttrib() and _mesa_PopClientAttrib().
|
|
|
|
| |
The former may point to the later.
|
|
|
|
|
|
| |
Don't really delete vertex array objects until the refcount hits zero.
At that time, unbind any pointers to VBOs.
(cherry picked from commit 32b851c80792623195069d7a41a5808cff3b2f6f)
|
|
|
|
|
|
| |
Every kind of object that can be shared by multiple contexts should be
refcounted.
(cherry picked from commit 1030bf0ded2a88a5e27f7a4d393c11cfde3d3c5a)
|
|
|
|
|
|
|
|
|
|
|
|
| |
For non-stereo visuals, which is all we support, we treat
GL_FRONT_LEFT as GL_FRONT. However, they are technically different,
and they have different enum values. Test for either one to determine
if we're in front-buffer rendering mode.
This fix was suggested by Pierre Willenbrock.
Signed-off-by: Ian Romanick <[email protected]>
(cherry picked from commit 2085cf24628be7cd297ab0f9ef5ce02bd5a006e2)
|
| |
|