Age | Commit message (Collapse) | Author |
|
The old code even falls apart for nr == 0 (which is caught earlier, but)!
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
|
|
|
|
|
|
|
|
Fixes regression from a08e612fd8e7ca2ac2fef8961e56e5b094033717
|
|
|
|
There is an issue with gcc 4.6.0 that leads to segfault/assert with mesa
due to ureg_src size, reshuffling the structure member to better better
alignment work around the issue.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47893
7.9 + 7.10 candidate
Signed-off-by: Jerome Glisse <jglisse@redhat.com>
|
|
so far only hw mipmap generation is testing on softpipe,
passes test added to piglit.
this requires another patch to mesa to let array textures mipmaps
even start to happen.
|
|
platform.system in SCons on Cygwin includes the OS version number.
Windows XP - CYGWIN_NT-5.1
Windows Vista - CYGWIN_NT-6.0
Windows 7 - CYGWIN_NT-6.1
Reduce all Cygwin platform variants to just 'cygwin' so anything
downstream can simply use 'cygwin' instead of the different full
platform names.
|
|
|
|
Make the s3tc upload code more generic.
Signed-off-by: Dave Airlie <airlied@redhat.com>
|
|
|
|
|
|
Saves us the explicit compare instruction needed with selp.
|
|
|
|
|
|
Before this, l[] access was a no-op.
|
|
|
|
|
|
They affect overlap tests even though they're actually empty.
|
|
Might be necessary if a block sneaks in somewhere, like a common
block for moves of phi sources after a loop break.
This is harmless and normally will be removed before emission.
|
|
In linear scan we can't allocate multiple values with different
live ranges at the same time to assign them consecutive regs.
Maybe we should just switch to graph coloring for all values ...
|
|
Fixes for example piglit/fbo-flushing and nexuiz' bloom effect.
|
|
Before, there were situations in which we never checked the fences
for completion (some loading screens for example) and thus never
released memory.
|
|
|
|
Wasn't sure if this still was necessary because the piglit test
started to fail at some point on nv50 where we already do this.
|
|
|
|
|
|
Except the reference to its own result.
|
|
Check if element was translated per element instead of per buffer.
|
|
buffer start.
The svga_update_state() mechanism is inadequate as it will always end up
flushing the primitives before processing the SVGA_NEW_COMMAND_BUFFER
dirty state flag.
|
|
This adds EXT_texture_array support to r600g, it passes the piglit
array-texture test but I suspect may not be complete.
It currently requires a kernel patch to fix the CS checker to allow
these, so you need to use R600_ARRAY_TEXTURE=true for now
to enable them.
Signed-off-by: Dave Airlie <airlied@redhat.com>
|
|
Fixes immediate Python exceptions with SCons on Cygwin.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Reported-by Chris Wilson <chris@chris-wilson.co.uk>
|
|
The spec says that the offsets in the vertex-fetch instructions need to be byte-aligned and makes no specification with regard to the required alignment of the offset and stride in the vertex resource constant register.
However, testing indicates that all three values need to be DWORD aligned.
|
|
|
|
|
|
|
|
|
|
|
|
Needs to track this ourself since because we get into a race condition with
the dri_util.c code on make current when rendering to the front buffer.
This is what happens:
Old context is rendering to the front buffer.
App calls MakeCurrent with a new context. dri_util.c sets
drawable->driContextPriv to the new context and then calls the driver make
current. st/dri make current flushes the old context, which calls back into
st/dri via the flush frontbuffer hook. st/dri calls dri loader flush
frontbuffer, which calls invalidate buffer on the drawable into st/dri.
This is where things gets wrong. st/dri grabs the context from the dri
drawable (which now points to the new context) and calls invalidate
framebuffer to the new context which has not yet set the new drawable as its
framebuffers since we have not called make current yet, it asserts.
|
|
Intel classic drivers switched to this, too, so it must be good.
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
|
|
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
|