| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
| |
So that messages are in sync with stderr.
|
|
|
|
| |
It was providing 1 too many for non power two values.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
I started looking into why _NEW_ARRAY punishes us, and while annotating
dependencies noticed that a bunch of dependencies were missing.
(cherry picked from master, commit e5f63c403b767f9974e8eb5d412c012b8a69287f)
|
| |
|
|
|
|
| |
More common. True fix would be to use whatever the screen supports though.
|
| |
|
|
|
|
| |
Move a chunk of code out of _mesa_error()
|
|
|
|
| |
Remove early and unused snprintf and where[] string.
|
|
|
|
|
|
| |
Buggy apps can generate thousands of mesa_error calls. Don't need
to keep calling getenv to retreive the same MESA_DEBUG string each
time.
|
|
|
|
|
| |
The texture object's border color used to be stored as GLchan but it's
been GLfloat for a while now.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
See also:
- http://bugs.python.org/issue6476
- http://scons.tigris.org/issues/show_bug.cgi?id=2449
|
| |
|
| |
|
| |
|
|
|
|
| |
otherwise we decrement indexes for all registers
|
| |
|
|
|
|
| |
Same story as in the tgsi_dump.c code (see prev commit).
|
|
|
|
|
|
|
|
| |
Fixes TGSI dump output when front/back-face register is declared.
Also, add some assertions to make sure the semantic/interpolate string
arrays have as many elements as there are tokens in the p_shader_tokens.h
file. That should catch problems like this in the future.
|
| |
|
|
|
|
| |
Includes the TGSI interpreter, but not the SSE/PPC/etc code generators.
|
|
|
|
| |
Based on a patch by [email protected]
|
|
|
|
| |
Avoid potential randomness in resulting texcoords.
|
| |
|
|
|
|
|
|
|
|
|
| |
The values 2147483648.0 and 4294967294.0 are too larget to be stored in single
precision floats. Forcing these to be singles causes bits to be lost, which
results in errors in some pixel transfer tests.
This fixes bug #22344.
(cherry picked from commit 70e72070fce6aa1e0918dcc62c1949465cee69f7)
|
| |
|
|
|
|
|
|
|
|
|
|
| |
When a function parameter is const-qualified we can avoid making a copy
of the actual parameter (we basically do a search/replace when inlining).
This is now done for array element params too, resulting in better code
(fewer MOV instructions).
We should allow some other types of function arguments here but let's be
conservative for the moment.
|
|
|
|
|
| |
The two indexes were mixed up when accessing a row of a matrix in an array
of matrices.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
two)
The semantics are a little different for shaders vs. fixed-function when
trying to use an incomplete texture. The fallback texture returning
(0,0,0,1) should only be used with shaders. For fixed function, the texture
unit is truly disabled/ignored.
Fixes glean fbo test regression.
(cherry picked from commit 01e16befd4809e3e93ee7855a4a5d7df9fe010d9)
(cherry picked from commit 51325f44d1e7e62b47795a79f8038d10dc5bc30b)
[anholt: squashed these two together from master, skipping the mess in between]
|
| |
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
| |
Of course glXGetVideoSyncSGI doesn't return the swap interval. The feature
only exists in the Mesa extension... which is the whole reason I created the
Mesa extension! Note that the Mesa extension allows drivers to default to a
swap interval of 0. If the Mesa extension exists, use its value. Only
consider the SGI extension when the Mesa extension is not available.
Fixes bug #22604.
|
|
|
|
|
|
|
| |
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.
|