summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* r300-gallium: Fix bad cast. Space accounting completely works now.Corbin Simpson2009-05-082-5/+2
| | | | Boy, is my face red. :C
* r300-gallium, radeon: BO handling fixes, some useful asserts.Corbin Simpson2009-05-082-3/+9
|
* radeon-gallium: Shut up Valgrind.Corbin Simpson2009-05-081-3/+3
|
* r300-gallium, radeon: A couple cleanups.Corbin Simpson2009-05-084-5/+11
| | | | Trying to track down goddamn bugs. :C
* r300-gallium: Finish space accounting.Corbin Simpson2009-05-084-26/+66
| | | | Still broken...
* i965: improve debug loggingRobert Ellison2009-05-083-14/+86
| | | | | | | | | | | | | | | | Looking for memory leaks that were causing crashes in my environment in a situation where valgrind would not work, I ended up improving the i965 debug traces so I could better see where the memory was being allocated and where it was going, in the regions and miptrees code, and in the state caches. These traces were specific enough that external scripts could determine what elements were not being released, and where the memory leaks were. I also ended up creating my own backtrace code in intel_regions.c, to determine exactly where regions were being allocated and for what, since valgrind wasn't working. Because it was useful, I left it in, but disabled and compiled out. It can be activated by changing a flag at the top of the file.
* i965: fix memory leak in context/renderbuffer region managementRobert Ellison2009-05-081-4/+60
| | | | | | | | | | | | | | | | | A temporary change to the intelMakeCurrent() function to make it work with frame buffer objects causes the static regions associated with the context (the front_region, back_region, and depth_region) to take on an additional reference, with no corresponding release. This causes a memory leak if a program repeatedly creates and destroys contexts. The fix is the corresponding hack, to unreference these regions when the context is deleted, but only if the framebuffer objects are still present and the same regions are still referenced within. Both sets of code have comment blocks referring to each other.
* i965: fix segfault on low memory conditionsRobert Ellison2009-05-081-0/+7
| | | | | | | When out of memory (in at least one case, triggered by a longrunning memory leak), this code will segfault and crash. By checking for the out-of-memory condition, the system can continue, and will report the out-of-memory error later, a much preferable outcome.
* mesa: Fixed a texture memory leakRobert Ellison2009-05-081-0/+3
| | | | | | | | | | | | The current texture for any particular texture unit is given an additional reference in update_texture_state(); but if the context is closed before that texture can be released (which is quite frequent in normal use, unless a program unbinds and deletes the texture and renders without it to force a call to update_texture_state(), the memory is lost. This affects general Mesa; but the i965 is particularly affected because it allocates a considerable amount of additional memory for each allocated texture.
* intel: Add a metaops version of glGenerateMipmapEXT/SGIS_generate_mipmaps.Eric Anholt2009-05-0810-76/+303
| | | | | | | In addition to being HW accelerated, it avoids the incorrect (black) rendering of the mipmaps that SW was doing in fbo-generatemipmap. Improves the performance of the mipmap generation and drawing in fbo-generatemipmap by 30%.
* intel: Put the constant texcoords used in metaops into a vbo.Eric Anholt2009-05-085-40/+102
| | | | | | | Make this be its own function for setup/teardown of the binding of these texcoords. No performance difference in the engine demo (I just felt dirty not using a VBO for this), and I think it should be more resilient to interference from current GL state.
* i965: const qualifiersBrian Paul2009-05-081-2/+2
|
* mesa: raise MAX_VARYING (number of shader varying vars) to 16Brian Paul2009-05-081-1/+1
| | | | 16 is the limit for now because of various 32-bit bitfields.
* mesa: assertions to check for too many vertex outputs or fragment inputsBrian Paul2009-05-081-0/+4
|
* glsl: check number of varying variables against the limitBrian Paul2009-05-081-4/+9
| | | | Link fails if too many varying vars.
* mesa: issue warning for out of bounds array indexesBrian Paul2009-05-081-0/+2
|
* i965: don't use GRF regs 126,127 for WM programsBrian Paul2009-05-082-5/+28
| | | | | | | They seem to be used for something else and using them for shader temps seems to lead to GPU lock-ups. Call _mesa_warning() when we run out of temps. Also, clean up some debug code.
* glsl: set vertex/fragment program Ids to aid with debuggingBrian Paul2009-05-081-0/+4
|
* mesa: more shader debug code (disabled)Brian Paul2009-05-081-0/+4
|
* mesa/st: keep surface_copy arguments positiveKeith Whitwell2009-05-082-3/+68
| | | | | | | The src/dest x,y, and w,h arguments of the pipe->surface_copy function are unsigned and the drivers aren't expecting negative (or extremly-large unsigned) values as inputs. Trim the requests at the state-tracker level before passing down.
* mesa/st: remove redundant call to st_finish in CopyTexSubImageKeith Whitwell2009-05-081-3/+0
| | | | | Rendering should already have been flushed, any synchronization will be done by the driver or memory manager.
* wgl: Export pixelformats with accumulation bits.José Fonseca2009-05-081-6/+8
|
* mesa/st: cope with non-ibo index data in st_draw_feedback.cKeith Whitwell2009-05-081-8/+15
| | | | | | Previously only non-indexed or indicies-in-a-vbo cases were handled in this code. This change adds the missing regular indices-in-memory case.
* util/upload: catch failures to map_range and return errorKeith Whitwell2009-05-081-13/+17
| | | | Caller may be able to do something about this - eg flush and retry.
* scons: mingw is broken with -O1 and higherKeith Whitwell2009-05-082-0/+4
|
* stw: fix potential uninitialized use of curctxKeith Whitwell2009-05-081-1/+1
|
* wgl: Enforce a minimum 1x1 framebuffer size.José Fonseca2009-05-081-8/+19
|
* wgl: Add assertion for missing function.José Fonseca2009-05-081-0/+1
|
* wgl: Remove unused variable.José Fonseca2009-05-081-1/+0
|
* mesa: Make _mesa_share_state thread safe.José Fonseca2009-05-081-2/+9
|
* wgl: Implement ShareLists.José Fonseca2009-05-084-7/+28
|
* nouveau: respect GALLIUM_STATE_TRACKERS_DIRSBen Skeggs2009-05-081-1/+1
|
* nouveau: remove dri1 code now we're using the dri state trackerBen Skeggs2009-05-0810-755/+5
|
* nouveau: use dri state tracker for dri1Ben Skeggs2009-05-086-2/+92
|
* mesa: make the array object save/remove functions staticBrian Paul2009-05-072-14/+7
|
* mesa: clean-up vertex array object VBO unbinding and delete/refcountingBrian Paul2009-05-071-31/+33
| | | | | Don't really delete vertex array objects until the refcount hits zero. At that time, unbind any pointers to VBOs.
* demos: delete vertex array objects upon exitBrian Paul2009-05-071-0/+2
|
* mesa: reference counting for gl_array_objectBrian Paul2009-05-074-14/+83
| | | | | Every kind of object that can be shared by multiple contexts should be refcounted.
* mesa: array object commentsBrian Paul2009-05-071-0/+5
|
* mesa: move the NullBufferObj from GLcontext to gl_shared_stateBrian Paul2009-05-0713-41/+50
| | | | | Since shared array objects may point to the null/default buffer object, the null/default buffer object should be part of the shared state.
* mesa: fix comments, s/texture/buffer/Brian Paul2009-05-071-2/+2
|
* vbo: in glDraw[Range]Element() code, check for out of bounds indexesBrian Paul2009-05-071-0/+7
| | | | | No-op the bad drawing command rather than go out of bounds and render garbage. Print a warning to alert the developer to the bad drawing call.
* mesa: remove unused gl_buffer_object::OnCard fieldBrian Paul2009-05-072-3/+0
|
* mesa: added gl_buffer_object::Written flag (for debug purposes)Brian Paul2009-05-072-0/+7
| | | | The flag is set when we data has been written into the buffer object.
* mesa: Compute gl_client_array->_MaxElement during array validationBrian Paul2009-05-074-40/+64
| | | | | | Used to be done in the glVertex/Normal/Color/etc/Pointer() calls but if the VBO was reallocated the size could change. New _NEW_BUFFER_OBJECT state flag.
* mesa: GLvector4f:: flags is a GLbitfield, update comments too.Brian Paul2009-05-072-5/+5
|
* mesa: add storage_count field to GLvector4f. Useful for debugging.Brian Paul2009-05-072-0/+2
|
* mesa: use array->BufferObj instead of ctx->Array.ArrayBufferObjBrian Paul2009-05-071-2/+2
| | | | No difference, but a little more understandable.
* mesa: added _ElementSize field to gl_client_arrayBrian Paul2009-05-072-0/+3
| | | | Will be handy for bounds checking later...
* mesa: use local var to make code a bit more conciseBrian Paul2009-05-071-36/+37
|
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-19 13:02:11 +0000