summaryrefslogtreecommitdiff
path: root/src
AgeCommit message (Collapse)Author
2009-01-10nouveau: Catch some more leaks.Younes Manton
2009-01-10g3dvl: Fix some memory leaks.Younes Manton
2009-01-10g3dvl: Allocate one set of bufs, let winsys rename them as necessary.Younes Manton
2009-01-10nouveau: Add busy() query, determines if BOs can be mapped immediately.Younes Manton
2009-01-10nouveau: Use PIPE_BUFFER_USAGE_CPU_* instead of custom.Younes Manton
2009-01-10g3dvl: Expand YCbCr to full RGB range by default.Younes Manton
2009-01-10g3dvl: Work around mplayer weirdness in XvMCPutSurface().Younes Manton
2009-01-10g3dvl: Flag textures holding incoming data as dynamic.Younes Manton
2009-01-10nouveau: Put dynamic textures in GART for CPU access and don't swizzle.Younes Manton
Also flag shadows as dynamic since they're for CPU access as well.
2009-01-10gallium: Define PIPE_TEXTURE_USAGE_DYNAMIC.Younes Manton
Knowing how the client intends to use the texture will give the driver the opportunity to optimize for such cases.
2009-01-10nouveau: Swizzle textures larger than nv04 SIFM limit in parts.Younes Manton
Limit of SIFM on nv40 is 1024x1024, not sure about others.
2009-01-10glsl: force creation of new scope for for-loop bodyBrian Paul
Fixes regression in progs/demos/convolution.c due to loop unrolling. This also allows the following to be compiled correctly: for (int i = 0; i < n; i++) { int i; ... } This fix is a bit of a hack, however. The better fix would be to change the slang_shader.syn grammar. Will revisit that...
2009-01-10glsl: replace 0/1 with GL_FALSE/GL_TRUEBrian Paul
2009-01-09swrast: Fix GL_ATI_separate_stencilIan Romanick
GL_ATI_separate_stencil is enabled by default for software rasterizers, but the extension functions weren't hooked up to the dispatch table.
2009-01-09draw: Add missing include.José Fonseca
2009-01-09xlib: move state tracker to glx/xlibKeith Whitwell
Also, remove makefile hacks.
2009-01-09glsl: make minimum struct size = 2, not 1Brian Paul
1-component structs such as "struct foo { float x; }" could get placed at any position within a register. This caused some trouble computing the field offset which assumed all struct objects were placed at R.x. It would be unusual to hit this case in normal shaders.
2009-01-09xlib: disable more cell calls when GALLIUM_CELL not definedKeith Whitwell
2009-01-09xlib: strip out some CI and overlay supportKeith Whitwell
2009-01-09xlib: strip out some overlay supportKeith Whitwell
2009-01-09xlib: strip out glXAllocateMemoryNV & friendsKeith Whitwell
2009-01-09xlib: combine and eliminate some header filesKeith Whitwell
2009-01-09st: build fixAlan Hourihane
2009-01-09glsl: fix typo in the vec2 += operator functionBrian Paul
2009-01-09mesa: set version string to 7.3-rc1Brian Paul
2009-01-09glsl: fix broken +=, -=, *=, /= operatorsBrian Paul
These functions need to return the final computed value. Now expressions such as a = (b += c) work properly. Also, no need to use __asm intrinsics in these functions. The resulting code is the same when using ordinary arithmetic operators and is more legible.
2009-01-09mesa: fix off-by-one bug in _mesa_delete_instructions()Brian Paul
2009-01-09i965: Fix GLSL FS DPH to return the right value instead of src0.w * src1.w.Eric Anholt
2009-01-09i965: Remove worrisome comment about _NEW_PROGRAM signaling fp change.Eric Anholt
Everything now depends on either BRW_NEW_FRAGMENT_PROGRAM or BRW_NEW_VERTEX_PROGRAM.
2009-01-09mesa: Remove _Active and _UseTexEnvProgram flags from fragment programs.Eric Anholt
There was a note in state.c about _Active deserving to die, and there were potential issues with it due to i965 forgetting to set _UseTexEnvProgram. Removing both simplifies things. Reviewed-by: Brian Paul <brianp@vmware.com>
2009-01-09i965: Remove dead brw_vs_tnl.cEric Anholt
2009-01-09i965: allow gl_FragData[0] usage when there's only one color bufferBrian Paul
If gl_FragData[0] is written but not gl_FragCOlor, use the former.
2009-01-09mesa: additional case in file_string()Brian Paul
2009-01-09glsl: pass GLcontext::Extension info down into GLSL preprocessorBrian Paul
Now the #extension directives can be handled properly.
2009-01-09glsl: bump up MAX_FOR_LOOP_UNROLL_COMPLEXITYBrian Paul
2009-01-09glsl: check that the fragment shader does not write both gl_FragColor and ↵Brian Paul
gl_FragData[]
2009-01-09i965: init dst reg RelAddr field to zeroBrian Paul
2009-01-09i965: Note when we drop saturate mode on the floor in a VP.Eric Anholt
2009-01-09i965: Add support for LRP in VPs.Eric Anholt
Bug #19226.
2009-01-09glsl: disable some unused functions (but don't remove just yet)Brian Paul
2009-01-09glsl: also unroll loops with variable declarations such as "for (int i = 0; ..."Brian Paul
2009-01-09glsl: remove dead codeBrian Paul
2009-01-09mesa: OSMesa Makefile fixes (use LIB_DIR)Brian Paul
2009-01-09glsl: loop unroll adjustmentsBrian Paul
Add a "max complexity" heuristic to allow unrolling long loops with small bodies and short loops with large bodies. The loop unroll limits may need further tweaking...
2009-01-09glsl: implement loop unrolling for simple 'for' loopsBrian Paul
Loops such as this will be unrolled: for (i = 0; i < 4; ++i) { body; } where 'body' isn't too large. This also helps to fix the issue reported in bug #19190. The problem there is indexing vector types with a variable index. For example: vec4 v; v[2] = 1.0; // equivalent to v.z = 1.0 v[i] = 2.0; // variable index into vector!! Since the for-i loop can be unrolled, we can avoid the problems associated with variable indexing into a vector (at least in this case).
2009-01-09mesa: Move var declaration to top of scope.Brian Paul
(cherry picked from commit 3740a06e28f4cd09e2a3dce2da60320aa9304df1)
2009-01-09Merge commit 'origin/gallium-0.2' into gallium-xlib-reworkKeith Whitwell
Conflicts: progs/glsl/Makefile
2009-01-08glsl: fix typo in the vec2 += operator functionBrian Paul
2009-01-08mesa: set version string to 7.3-rc1Brian Paul
2009-01-08glsl: fix broken +=, -=, *=, /= operatorsBrian Paul
These functions need to return the final computed value. Now expressions such as a = (b += c) work properly. Also, no need to use __asm intrinsics in these functions. The resulting code is the same when using ordinary arithmetic operators and is more legible.