| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
(cherry picked from commit 88c01a15da5639dd68a6a0133724994cb66f1316)
|
|
|
|
| |
As reported and initially tested by MrCooper.
|
| |
|
|
|
|
|
|
| |
Stride == 0 means that we value for first vertex should be copied to every other vertices (e.g. constant color).
This fixes glean/vertProg1 and sauerbraten with enabled shaders.
|
| |
|
| |
|
|
|
|
|
| |
Even after fixing bugs in this code, it doesn't make me feel any cleaner.
Fixes piglit stencil-drawpixels.
|
| |
|
|
|
|
| |
This state flag has been unused since the ffvertex_prog move to core.
|
|
|
|
|
|
|
| |
Otherwise, a pointer greater than the size would underflow and give a large
maximum element.
Reviewed-by: Brian Paul <[email protected]> (previous version)
|
|\ |
|
| |
| |
| |
| |
| | |
Also fix one case where a 32 bit depth value was incorrectly converted to a
combined depth/stencil value.
|
| |
| |
| |
| |
| | |
Such visuals are subject to automatic compositing in the X server, so DRI1
can't render to them properly.
|
| |
| |
| |
| | |
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.
|
| |
| |
| |
| |
| |
| |
| | |
Ensure no other thread is accessing a framebuffer when it is being destroyed by
acquiring both the global and per-framebuffer mutexes. Normal access only
needs the global lock to walk the linked list and acquire the per-framebuffer
mutex.
|
| |
| |
| |
| |
| | |
Fixes wglthreads -- the 2nd thread MakeCurrent call was trying to flush
the first thread context while still in use.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
According to
http://blogs.msdn.com/oldnewthing/archive/2008/01/15/7113860.aspx
WM_SIZE is generated from WM_WINDOWPOSCHANGED by DefWindowProc so it
can be masked out by the application.
Also there were some weird bogus WM_SIZE 0x0 messages when starting
sharedtex_mt which we don't get like this.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
the driver used to overwrite grf0 then use implicit move by send instruction
to move contents of grf0 to mrf1. However, we must not overwrite grf0 since
it's still used later for fb write.
Instead, do the move directly do mrf1 (we could use implicit move from another
grf reg to mrf1 but since we need a mov to encode the data anyway it doesn't
seem to make sense).
I think the dp_READ/WRITE_16 functions may suffer from the same issue.
While here also remove unnecessary msg_reg_nr parameter from the dataport
functions since always message register 1 is used.
|
| |
| |
| |
| |
| |
| |
| | |
Thanks to branching, the state of c->current_const[i].index at the point
of emitting constant loads for this instruction may not match the actual
constant currently loaded in the reg at runtime. Fixes a regression in my
GLSL program for idr's class since b58b3a786aa38dcc9d72144c2cc691151e46e3d5.
|
|\ \ |
|
| | |
| | |
| | |
| | | |
Import of the OpenVG 1.0 state tracker for Gallium.
|
| | |
| | |
| | |
| | | |
plus it saves us a cacheline in the cso
|
| | |
| | |
| | |
| | | |
reported by clang static analyzer
|
| | |
| | |
| | |
| | | |
reported by clang static analyzer
|
| | |
| | |
| | |
| | | |
found by the clang static analyzer
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The problem is if we find out later we don't have any cmdbuf space but
we've already written the arrays to the DMA buffer object, we end up
emitting the current cmdbuf which has references to the current DMA object
we then send that to the hw and we can't reference the arrays we just emitted
to the old DMA buffer. things go bad, crash boom.
This can probably be tuned further + swtcl probably needs some fixes
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
This moves a big chunk of the space checking code into libdrm so
it can be shared by the DDX.
|
| | |
| | |
| | |
| | | |
Fixes flush during validation, in case a buffer is double-validated.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- don't limit vertex count if we are using indices
- max indices count is 65535 not 65536
- remove some comments that don't apply anymore
- remove unreachable code
|
|\ \ \
| | |/
| |/|
| | |
| | |
| | | |
Conflicts:
src/mesa/main/dlist.c
src/mesa/vbo/vbo_save_api.c
|
| | |
| | |
| | |
| | |
| | | |
Fixes assertion failure when binding depth/stencil texture to FBO stencil
attachment.
|
| | |
| | |
| | |
| | |
| | |
| | | |
gl_NormalMatrix is the inverse transpose of the modelview matrix, but
as every matrix here needs to be transposed, we end up with
{MODELVIEW_MATRIX, INVERSE}.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is a tweak to a previous fix -- it's not necessary to actually
advertise this extension to prevent these games from crashing -- they
ignore the extension string anyway. It's sufficient to just have
GetProcAddress return some dummy function addresses for SwapInterval.
Given we don't really implement this funcitonality, this is a better
fix.
|
| | |
| | |
| | |
| | |
| | | |
Some applications create several HDCs for the same window, so spite the WGL
API is geared towards HDCs it is not reliable searching by HDC.
|
| | | |
|
| | |
| | |
| | |
| | | |
Fix compile breakage on Linux.
|
| | |
| | |
| | |
| | | |
Propogate changes to enums.c back up to the python source.
|
| |\ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
progs/trivial/Makefile
Pull in a minimal version of statechange shortcircuiting in display
list compilation. This affects only glMaterial and glShadeModel state,
and includes quite a few tests to exercise various tricky cases.
If this goes well, will consider extending to all state in the future.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Where vbo save nodes are terminated with a call to DO_FALLBACK(), as in
the case of a recursive CallList which is itself within a Begin/End pair,
there two problems:
1) The display list node's primitive information was incorrect, stating
the cut-off prim had zero vertices
2) On replay, we would get confused by a primitive that started in a
node, but was terminated by individual opcodes.
This change fixes the first problem by correctly terminating the last
primitive on fallback, and the second by forcing the display list to
use the Loopback path, converting all nodes into immediate-mode rendering.
The loopback fix is a performance hit, but avoiding this would require
a fairly large rework of this code.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Only short-circuit material call if *all* statechanges from this call
are cached. Some material calls (eg with FRONT_AND_BACK) change more
than one piece of state -- need to check all of them before returning.
Also, Material calls are legal inside begin/end pairs, so don't need
to be as careful about begin/end state as with regular statechanges
(like ShadeModel) when caching. Take advantage of this and do better
caching.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Statechanges which occur before the first End in a display list may
not be replayed when the list is called, in particular if it is called
from within a begin/end pair.
Recognize vulnerable statechanges and do not use them to fill in the
state cache.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When compiling a display list containing a CallList, it is necessary to
invalidate any assumption about the GL state after the recursive call
completes.
|
| | |\ \
| | | | |
| | | | |
| | | | | |
Need this to pick up fixes for per-vertex materials.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Reorganization of ShadeModel to avoid flushing vertices too often
ended up never flushing vertices due to omitted line of code.
|