| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
If the renderbuffer orientation is Y=0=TOP we need to invert the dstY
position.
|
|
|
|
|
|
|
|
|
|
|
|
| |
State tracker currently backs GL_RGB textures with RGBA almost always.
This means we need to maintain A==1 in these textures to give correct GL_RGB
sampling results.
This change offloads the RGBA->RGB copy to hardware using the new writemask
version of u_blit_pixels.
More src/dstLogical/dstActual triples could be shifted to hardware by
this technique in future patches.
|
|
|
|
|
|
|
| |
When adding a new bitmap to the cache we have to check if the Z value is
changing and flush first if it is.
This is a modified version of a patch from Justin Dou <[email protected]>
|
|
|
|
|
|
| |
We now handle the case of blitting Z+stencil to/from combined Z/stencil
surfaces. But Z-only or stencil-only and separate depth/stencil surfaces
are not yet implemented.
|
|
|
|
|
|
|
|
|
| |
Need to check for Y inversion separately for src/dest buffers.
If both the src and dest regions are upside down, make them right-side
up for a better chance at a fast path.
progs/tests/copypixrate -blit is much faster now.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Windows opengl32.dll calls glFinish prior to every swapbuffers, which
makes it pretty hard to get decent performance...
Work around by mapping finish to flush on PIPE_OS_WINDOWS. This is
conformant, though it might confuse poorly-written benchmarks which
attempt to measure a single event rather than figuring out the rate of
continuous processing.
|
|
|
|
|
| |
Some apps enable scissor but set the rectangle to the dimensions of
the window. Don't let this force us onto a slower clear path.
|
| |
|
|
|
|
| |
It was providing 1 too many for non power two values.
|
| |
|
|
|
|
| |
otherwise we decrement indexes for all registers
|
| |
|
| |
|
|
|
|
|
| |
Also fix one case where a 32 bit depth value was incorrectly converted to a
combined depth/stencil value.
|
|
|
|
| |
Fixes potential crash when SwapBuffers is called but there's no back buffer.
|
|
|
|
|
| |
fix the cases when fog coord/front face/point coord are used in the same
shader.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
mesa allocates both frontface and pointcoord registers within the fog
coordinate register, by using swizzling. to make it cleaner and easier
for drivers we want each of them in its own register. so when doing
compilation from the mesa IR to tgsi allocate new registers for both
and add new semantics to the respective declarations.
|
|
|
|
| |
As prescribed by ARB_map_buffer_range.
|
| |
|
|
|
|
| |
Fixes leak running compiz with direct rendering.
|
|
|
|
|
|
|
|
|
|
| |
The first time a context is bound to a drawable, the viewport and scissor
bounds are initialized to the buffer's size. This is actually a bit tricky.
A new _mesa_check_init_viewport() function is called in several places
to check if the viewport has been initialized. We also use a new
ctx->ViewportInitialized flag instead of the overloaded
ctx->FirstTimeCurrent flag.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Before, if a vertex shader's outputs didn't exactly match a fragment
shader's inputs we could wind up with invalid TGSI shader declarations.
For example:
Before patch:
DCL OUT[0], POSITION
DCL OUT[1], COLOR[1]
DCL OUT[2], GENERIC[0]
DCL OUT[3], GENERIC[0] <- note duplicate [0]
DCL OUT[4], GENERIC[2]
After patch:
DCL OUT[0], POSITION
DCL OUT[1], COLOR[1]
DCL OUT[2], GENERIC[0]
DCL OUT[3], GENERIC[1]
DCL OUT[4], GENERIC[2]
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
touching the depth component.
|
|
|
|
|
|
| |
Actually, after spotting this problem, I realized this is unreachable
code. However don't bother to enable this fast path now, given the normal
path is working just fine.
|
|
|
|
|
|
|
| |
Reversed component order.
This fixes glean depthStencil test failures for PIPE_FORMAT_Z24S8_UNORM
visuals.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
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.
|
|
|
|
|
| |
Prevents segmentation fault when trying to set the viewport/scissor
after a context/drawable visual mismatch.
|
|
|
|
| |
The stride needs to be in texels, not bytes.
|
|
|
|
| |
We were passing a GL texture target instead of a pipe_texture_target enum.
|