aboutsummaryrefslogtreecommitdiffstats
path: root/src/mesa
Commit message (Collapse)AuthorAgeFilesLines
...
* | mesa: vbo code reformatting, clean-up, commentsBrian Paul2009-05-071-43/+52
| |
* | mesa: add GL_DOUBLE case in _mesa_sizeof_type()Brian Paul2009-05-071-0/+2
| |
* | mesa: in vbo split code, map buffers read-only, not write-onlyBrian Paul2009-05-071-6/+6
| | | | | | | | And use GL_ELEMENT_ARRAY_BUFFER where appropriate.
* | mesa: limit number of error raised by invalid GL_TEXTURE_MAX_ANISOTROPY_EXTBrian Paul2009-05-071-2/+4
| |
* | tnl: added some clip debug/print code (disabled)Brian Paul2009-05-071-0/+19
| |
* | mesa: reformatting, updated comments, const-correctnessBrian Paul2009-05-072-59/+50
| |
* | tnl: replace 0x3f with CILP_FRUSTUM_BITSBrian Paul2009-05-071-3/+3
| |
* | i965: relAddr local var (to make debug/test a little easier)Brian Paul2009-05-071-5/+6
| |
* | Merge branch 'mesa_7_5_branch'Brian Paul2009-05-073-22/+75
|\|
| * swrast: fix span clipping bugBrian Paul2009-05-072-22/+71
| | | | | | | | | | If a horizontal span of pixels was located at x < 0 we could sometimes read/write outside of renderbuffer bounds.
| * mesa: unmap buffer objects during context tear-downBrian Paul2009-05-071-0/+4
| |
* | i965: Remove bad constant buffer constant-reg-already-loaded optimization.Eric Anholt2009-05-061-13/+11
| | | | | | | | | | | | | | 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.
* | intel: Unmap buffers if needed at DeleteBuffer time.Eric Anholt2009-05-061-1/+10
| | | | | | | | | | | | | | This fixes a crash in glean's pbo test, which tripped over the assert when a context was destroyed while a buffer was still mapped (Mesa doesn't call UnmapBuffer in that case). Regression in c6bde8873fbda6d8467600b7491d8543c75b0509
* | mesa: remove unnecessary buffer size checkBrian Paul2009-05-061-8/+0
| |
* | mesa: code consolidation in glDraw[Range]Elements() validationBrian Paul2009-05-061-26/+22
| |
* | mesa: new comments, minor reformattingBrian Paul2009-05-061-7/+20
| |
* | mesa: use elementBuf local var instead of ctx->Array.ElementArrayBufferObjBrian Paul2009-05-061-1/+1
| | | | | | | | Makes no real difference, but more consistant.
* | i965: Remove the forced lack of caching for renderbuffer surface state.Eric Anholt2009-05-061-11/+8
| | | | | | | | | | | | | | | | | | This snuck in with the multi-draw-buffers commit, and is a major penalty to performance. It doesn't appear to be required, as the only dependency the surface BO has is on the state key (and if there's some other dependency, it should just be in the key). This brings openarena performance up to almost 2% faster than Mesa 7.4.
* | i965: Remove _NEW_PROGRAM from brw_wm_surfaces setup dependencies.Eric Anholt2009-05-061-2/+1
| | | | | | | | This was a leftover from the brw_wm_constant_buffer change.
* | mesa: be smarter about allocating vert/frag program constantsBrian Paul2009-05-061-25/+76
| | | | | | | | | | | | | | Try to re-use constants/literals more often to make best use of the constant buffer space. See bug 21354.
* | i965: Split WM constant buffer update from other WM surfaces.Eric Anholt2009-05-065-90/+95
| | | | | | | | | | | | | | | | This can avoid re-uploading constant data when it isn't necessary, and is a step towards not updating other surfaces just because constants change. It also brings the upload of the constant buffer next to the creation. This brings openarena performance up another 4%, to 91% of the Mesa 7.4 branch.
* | i965: Disentangle VS constant surface state from WM surface state.Eric Anholt2009-05-067-186/+255
| | | | | | | | | | Also, only create VS surface state if there's a VS constant buffer to be uploaded, and set the contents of the buffer at the same time as creation.
* | i965: Don't create constant buffers if they won't be used.Eric Anholt2009-05-061-1/+17
| | | | | | | | | | | | | | | | Really, the creation and upload of constants should be in the same place, since they should only happen together, and a state flag should be triggered by them so that we don't thrash state around so much for just updating constants. But this still recovers openarena performance by another 19%, leaving us 16% behind Mesa 7.4 branch.
* | mesa: only use fallback texture when using shaders, not fixed-function (take ↵Brian Paul2009-05-051-8/+14
| | | | | | | | | | | | | | | | | | | | | | 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.
* | Revert "mesa: only use fallback texture when using shaders, not fixed-function"Brian Paul2009-05-051-14/+8
| | | | | | | | | | | | This reverts commit a0edbfb28fb2e670c657d52190a7e8b1ccf4f46e. This patch didn't completely fix the problem. The next patch will.
* | mesa: only use fallback texture when using shaders, not fixed-functionBrian Paul2009-05-051-8/+14
| | | | | | | | | | | | | | | | 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. Fixes glean fbo test regression.
* | mesa: only use fallback texture when using shaders, not fixed-functionBrian Paul2009-05-051-4/+4
| | | | | | | | | | | | | | | | 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. Fixes glean fbo test regression.
* | mesa: minor simplification in enable_texture(), updated commentsBrian Paul2009-05-051-3/+5
| |
* | mesa: more complete fix for transform_invarient glitchesKeith Whitwell2009-05-056-11/+153
| | | | | | | | | | | | Add a new flag mvp_with_dp4 in the context, and use that to switch both ffvertex.c and programopt.c vertex transformation code to either DP4 or MUL/MAD implementations.
* | mesa/main: set PREFER_DP4 to match position_invarient codeKeith Whitwell2009-05-051-1/+1
| | | | | | | | | | | | | | | | This is a quick fix for z fighting in quake4 caused by the mismatch between vertex transformation here and in the position_invarient code. Full fix would be to make this driver-tunable and adjust both position_invarient and ffvertex_prog.c code to respect driver preferences.
* | mesa: also print program params/constants when dumping shaders to diskBrian Paul2009-05-041-0/+4
| |
* | mesa: remove some unfinished/devel codeBrian Paul2009-05-041-92/+0
| |
* | mesa: in glReadBufer() set _NEW_BUFFERS, not _NEW_PIXELBrian Paul2009-05-016-6/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since GL_READ_BUFFER is historically part of the gl_pixel_attrib group it made sense to signal changes with _NEW_PIXEL. But now with FBOs it's also part of the framebuffer state. Now _NEW_PIXEL strictly indicates pixels transfer state changes. This change avoids framebuffer state validation when any random bit of pixel-transfer state is set. DRI drivers updated too: don't check _NEW_COLOR when updating framebuffer state. I think that was just copied from the Xlib driver because we care about dither enable/disable state there.
* | Merge branch 'mesa_7_5_branch'Brian Paul2009-05-012-6/+27
|\|
| * st: create renderbuffer's pipe_surface in st_render_texture()Brian Paul2009-05-011-1/+11
| | | | | | | | | | | | Previously we created the pipe_surface during framebuffer validation. But if we did a glCopyTex[Sub]Image() before anything else we wouldn't yet have the surface. This fixes that.
| * mesa: fix state validation bug for glCopyTex[Sub]Image()Brian Paul2009-05-011-5/+16
| | | | | | | | | | We need to make sure the framebuffer state is up to date to make sure we read pixels from the right buffer when doing a texture image copy.
| * mesa: remove -devel suffix from versionBrian Paul2009-05-011-1/+1
| |
* | st: if st_swapbuffers() is called for single-buffered visual don't crashBrian Paul2009-05-011-1/+19
| | | | | | | | Furthermore, return pointer(s) to the front color buffer(s).
* | st: when creating an on-demand front color buffer, init to back buffer imageBrian Paul2009-05-011-1/+31
| | | | | | | | | | | | When we create a new front color buffer (user called glDrawBuffer(GL_FRONT)) initialize it to the contents of the back buffer. Any previous call to SwapBuffers() would have done that in effect, so make it reality.
* | st: added st_renderbuffer::defined flagBrian Paul2009-05-016-2/+28
| | | | | | | | | | | | | | | | | | | | Indicates whether there's defined image contents, or garbage/don't care. This is set when we draw into a renderbuffer and cleared when we resize/ reallocate a renderbuffer or do a buffer swap (back buffer becomes undefined). We use this to determine whether the front color buffer has been drawn to, and whether to display its contents upon glFlush/Finish(), when the new st_swapbuffers() function is used.
* | mesa: fix commentBrian Paul2009-05-011-1/+1
| |
* | set: new st_swapbuffers() which does a true front/back buffer swapBrian Paul2009-05-012-0/+83
| | | | | | | | | | The pointers to the front/back renderbuffers are exchanged. This new function isn't actually used yet...
* | Test either GL_FRONT_LEFT or GL_FRONT for front-buffer renderingIan Romanick2009-05-011-1/+2
| | | | | | | | | | | | | | | | | | | | | | 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]>
* | st: when double buffered, only create front color buffer on demandBrian Paul2009-05-012-8/+109
| | | | | | | | | | Before we always created the front color buffer, even if was never used. This can save some memory.
* | Merge branch 'const-buffer-changes'Brian Paul2009-05-0119-232/+505
|\ \ | | | | | | | | | | | | | | | | | | | | | Conflicts: src/mesa/drivers/dri/i965/brw_curbe.c src/mesa/drivers/dri/i965/brw_vs_emit.c src/mesa/drivers/dri/i965/brw_wm_glsl.c
| * | mesa: added _mesa_check_soa_dependencies() functionBrian Paul2009-04-292-0/+53
| | | | | | | | | | | | | | | This function will check an instruction to see if there's data dependencies between the dst and src registers if executed in an SOA manner.
| * | i965: #include prog_print.h to silence warningBrian Paul2009-04-271-0/+1
| | |
| * | i965: only upload constant buffer data when we actually need the const bufferBrian Paul2009-04-276-17/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | Make the use_const_buffer field per-program and only call the code which updates the constant buffer's data if the flag is set. This should undo the perf regression from 20f3497e4b6756e330f7b3f54e8acaa1d6c92052 (cherry picked from master, commit dc9705d12d162ba6d087eb762e315de9f97bc456)
| * | i965: rework GLSL/WM register allocationBrian Paul2009-04-242-48/+168
| | | | | | | | | | | | | | | | | | | | | | | | | | | Use a bitvector of used/free flags. If we run out of temps, examine the live intervals of the temp regs in the program and free those which are no longer alive. Also, enable the new WM const buffer code.
| * | mesa: refactor code and make _mesa_find_temp_intervals() publicBrian Paul2009-04-242-22/+144
| | |