summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* r300g: s/false/FALSE/Corbin Simpson2009-11-072-9/+9
| | | | Also s/true/TRUE/
* r300g: Clean up indexbuf render, switch to RELOC macro.Corbin Simpson2009-11-071-15/+17
|
* r300g: Clean up r300_setup_vertex_buffers.Corbin Simpson2009-11-071-15/+13
|
* r300g: Don't pass hw_prim around in the context.Corbin Simpson2009-11-075-81/+74
| | | | And some other fixes.
* r300g: Use common state funcs for translating vert formats.Corbin Simpson2009-11-071-72/+6
|
* r300g: don't hang GPU on misbehaving appsMaciej Cencora2009-11-071-0/+6
|
* r300g: VBOs WIPMaciej Cencora2009-11-0710-109/+477
|
* r300g: add missing flushMaciej Cencora2009-11-071-0/+2
|
* r300g: enable CS dumpingMaciej Cencora2009-11-071-2/+2
|
* r300g: move vborender context function to seperate fileMaciej Cencora2009-11-072-1/+6
| | | | | | r300g: Un-migrate r300_draw_render. It'll make maintaining the SW TCL path easier.
* mesa: move code after declbrian2009-11-071-1/+2
| | | | Fixes bug 24967.
* nv50: enable all 32 threads of a warpChristoph Bumiller2009-11-071-1/+3
| | | | | This should be the default setting. See also 7d967b9b7c08aea2a471c5bf6aced8bfafdae874.
* i965: Use Compr4 instruction compression mode on G4X and newer.Eric Anholt2009-11-063-17/+29
| | | | | | | No statistically significant performance difference at n=3 with either openarena or my GL demo, but cutting program size seems like a good thing to be doing for the hypothetical app that has a working set near icache size.
* i965: Share min/max between brw_wm_emit.c and brw_wm_glsl.cEric Anholt2009-11-063-60/+72
|
* i965: Share emit_fb_write() between brw_wm_emit.c and brw_wm_glsl.cEric Anholt2009-11-064-127/+40
| | | | This should fix issues with antialiased lines in GLSL.
* i965: Share most of the WM functions between brw_wm_glsl.c and brw_wm_emit.cEric Anholt2009-11-063-297/+109
| | | | | The PINTERP code should be faster for brw_wm_glsl.c now since brw_wm_emit.c's had been improved, and pixel_w should no longer stomp on a neighbor to dst.
* i965: Share math functions between brw_wm_glsl.c and brw_wm_emit.c.Eric Anholt2009-11-063-221/+111
|
* i965: Share the sop opcodes between brw_wm_glsl.c and brw_wm_emit.c.Eric Anholt2009-11-063-74/+29
|
* i965: Share OPCODE_MAD between brw_wm_glsl.c and brw_wm_emit.cEric Anholt2009-11-063-30/+13
|
* i965: Share the DP3, DP4, and DPH between brw_wm_glsl.c and brw_wm_emit.cEric Anholt2009-11-063-99/+33
|
* i965: Add generic GLSL code for unaliasing a 3-arg opcode, and share LRP code.Eric Anholt2009-11-063-45/+71
|
* i965: Use a normal alu1 emit for OPCODE_TRUNC.Eric Anholt2009-11-062-34/+2
|
* i965: Share basic ALU ops between brw_wm_glsl and brw_wm_emit.cEric Anholt2009-11-063-117/+38
| | | | | This drops support for get_src_reg_imm in these, but the prospect of getting brw_wm_pass*.c onto our GLSL path is well worth some temporary pain.
* i965: Collect GLSL src/dst regs up in generic code.Eric Anholt2009-11-062-7/+17
| | | | | | | | This matches brw_wm_emit.c, which we'll be using shortly. There's a possible penalty here in that we'll allocate registers for unused channels, since we aren't doing ref tracking like brw_wm_pass*.c does. However, my measurements on GM965 don't show any for either OA or UT2004 with the GLSL path forced.
* st/xorg: implement batching for the composite opZack Rusin2009-11-064-90/+161
| | | | something is broken so disabled for now
* st/xorg: batch solid fill requestsZack Rusin2009-11-064-95/+66
| | | | | instead of lots of very small transfers, one larger is a lot better for performance
* st/xorg: start accumulating vertices in a common bufferZack Rusin2009-11-062-48/+88
|
* st/xorg: use quads instead of triangle fansZack Rusin2009-11-061-4/+4
| | | | easier to split, accumulate and batch those
* st/xorg: make the buffer size globalZack Rusin2009-11-061-1/+9
|
* mesa: Reduce the source channels considered in optimization passes.Eric Anholt2009-11-061-1/+40
| | | | | | | Depending on the writemask or the opcode, we can often trim the source channels considered used for dead code elimination. This saves actual instructions on 965 in the non-GLSL path for glean glsl1, and cleans up the writemasks of programs even further.
* mesa: Fix remove_instructions to successfully remove when removeFlags[0].Eric Anholt2009-11-061-0/+6
| | | | | This fixes the dead code elimination to work on the particular code mentioned in the previous commit.
* mesa: Add an optimization path to remove use of pointless MOVs.Eric Anholt2009-11-061-1/+83
| | | | | | | | | | | | | | | | | | GLSL code such as: vec4 result = {0, 1, 0, 0}; gl_FragColor = result; emits code like: 0: MOV TEMP[0], CONST[0]; 1: MOV OUTPUT[1], TEMP[0]; and this replaces it with: 0: MOV TEMP[0], CONST[0]; 1: MOV OUTPUT[1], CONST[0]; Even when the dead code eliminator fails to clean up a now-useless MOV instruction (since it doesn't do live/dead ranges), this should at reduce dependencies.
* mesa: Fix up the remove_dead_code pass to operate on a channel basis.Eric Anholt2009-11-061-28/+56
| | | | | | | This cleans up a bunch of instructions in GLSL programs to have limited writemasks, which would translate to wins in shaders that hit the i965 brw_wm_glsl.c path by depending less on in-driver optimizations. It will also help hit other optimization passes I'm looking at.
* intel: better front color buffer test in intelClear()Brian Paul2009-11-061-2/+3
|
* i965: Always pass the size argument to brw_cache_data.Eric Anholt2009-11-066-57/+21
| | | | | This keeps the individual state files from having to export their structures for brw_state_cache initialization.
* intel: Finish removing the fallback code for bug #16697.Eric Anholt2009-11-061-6/+2
| | | | I fixed it properly as of 7216679c1998b49ff5b08e6b43f8d5779415bf54.
* intel: Don't validate in a texture image used as a render target.Eric Anholt2009-11-063-11/+15
| | | | | Otherwise, we could lose track of rendering to that image, which could easily happen during mipmap generation.
* mesa: Attempt to pair up Driver.RenderTexture and FinishRenderTexture()Eric Anholt2009-11-061-0/+4
| | | | | | | | | | This is probably not 100% complete (bind vs unbind may still not pair up exactly), but it should help out drivers which are relying on FinishRenderTexture to be called when we're done rendering to a particular texture level, not just when we're done rendering to the object at all. This is the case for the one consumer of FinishRenderTexture() so far: the gallium state tracker. Noticed when trying to make use of FRT() in the intel driver.
* intel: Clean up some extra struct indirection in finalize.Eric Anholt2009-11-061-2/+1
|
* intel: Use _mesa_get_current_tex_object() to clean up TFP path.Eric Anholt2009-11-061-4/+4
|
* intel: Remove duplicated arguments from intel_miptree_match_image().Eric Anholt2009-11-063-10/+7
|
* i965: Remove an XXX comment for testing some code that seems to work.Eric Anholt2009-11-061-1/+0
|
* intel: Remove obsolete comment about GEM in the spans code.Eric Anholt2009-11-061-1/+0
|
* intel: Use PIPE_CONTROL on gen4 hardware for doing pipeline flushing.Eric Anholt2009-11-067-51/+37
| | | | | | This should do all the things that MI_FLUSH did, but it can be pipelined so that further rendering isn't blocked on the flush completion unless necessary.
* Make a convenient int for what chipset generation we're on.Eric Anholt2009-11-065-9/+20
| | | | | | gen2/3/4 are easier to say than "8xx, 915-945/g33/pineview, 965/g45/misc", and compares on generation are often easier than stringing together a bunch of chipset checks.
* Merge branch 'mesa_7_6_branch'Ian Romanick2009-11-068-570/+508
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This should fix the memory leaks in the assembly parser without the regressions. The conflicts in program_lexer.l were related to changes in returning strings between the branches (always return IDENTIFIER vs. returing either IDENTIFIER or USED_IDENTIFIER). The conflicts in program_parse.y were related to two changes in master One change prints a variable name in an error message. The other change adds outputVarSize to the OUTPUT_statement rule. The cause the position of the IDENTIFIER to change from $2 to $3. Conflicts: src/mesa/shader/lex.yy.c src/mesa/shader/program_lexer.l src/mesa/shader/program_parse.tab.c src/mesa/shader/program_parse.y
| * ARB prog parser: Regenerate parser from previous commits.Ian Romanick2009-11-061-242/+268
| |
| * ARB prog parser: Release old program string in ↵Ian Romanick2009-11-062-4/+6
| | | | | | | | | | | | | | | | | | _mesa_parse_arb_{fragment,vertex}_program The program structure passed to _mesa_parse_arb_program is just a place holder. The stings that actually need to be released are only known to the functions calling _mesa_parse_arb_program, so they should be freed there.
| * ARB prog parser: Release strings returned from the lexer that don't need to ↵Ian Romanick2009-11-061-1/+27
| | | | | | | | be kept
| * Revert "ARB prog parser: Fix epic memory leak in lexer / parser interface"Ian Romanick2009-11-065-337/+207
| | | | | | | | | | | | | | | | This reverts commit 93dae6761bc90bbd43b450d2673620ec189b2c7a. This change was completely broken when the parser uses multiple strings in a single production. It would be nice if bug fixes could initially land somewhere other than the stable branch.
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-23 17:25:58 +0000