summaryrefslogtreecommitdiffstats
path: root/src/mesa/glapi/dispatch.h
Commit message (Collapse)AuthorAgeFilesLines
* glapi: fix incorrect/missing return types for glFenceSync(), glClientWaitSync()Brian Paul2009-09-031-2/+2
|
* ARB sync: Regenerate files from previous commitIan Romanick2009-09-031-219/+268
|
* Regenerate files for GL_APPLE_flush_buffer_rangeIan Romanick2009-08-141-8/+36
|
* mesa: regenerated files related to GL_ARB_vertex_array_objectBrian Paul2009-06-191-216/+230
|
* Merge branch 'ext-provoking-vertex'Brian Paul2009-06-191-6/+13
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: docs/relnotes-7.6.html progs/tests/Makefile src/gallium/drivers/softpipe/sp_prim_vbuf.c src/glx/x11/indirect.c src/mesa/glapi/Makefile src/mesa/glapi/dispatch.h src/mesa/glapi/glapioffsets.h src/mesa/glapi/glapitable.h src/mesa/glapi/glapitemp.h src/mesa/glapi/glprocs.h src/mesa/main/dlist.c src/mesa/main/enums.c src/mesa/sparc/glapi_sparc.S src/mesa/x86-64/glapi_x86-64.S src/mesa/x86/glapi_x86.S
| * mesa: GL API changes for GL_EXT_provoking_vertexBrian Paul2009-05-281-6/+13
| | | | | | | | This creates the new glProvokingVertexEXT() entrypoint.
* | mesa: regenerated files for GL_ARB_map_buffer_rangeBrian Paul2009-06-081-215/+229
| |
* | glapi: regenerated files for GL_ARB_copy_bufferBrian Paul2009-06-021-214/+221
|/
* regenerate glapiRoland Scheidegger2009-03-121-54/+82
|
* mesa: regenerated GL API filesBrian Paul2009-01-221-210/+217
|
* mesa: fix some misc breakage caused by editing auto-generated files rather ↵Brian Paul2008-11-101-0/+2
| | | | | | | | than the python generators Specifically: #include "glapitable.h" in src/mesa/main/glapi/dispatch.h Call _mesa_bsearch() in src/mesa/main/enums.c.
* GLX: fix out-of-bounds memory issue in indirect glAreTexturesResident()Brian Paul2008-11-101-3/+0
| | | | | | | | | | | | | | | | See bug 18445. When getting array results, __glXReadReply() always reads a multiple of four bytes. This can cause writing to invalid memory when 'n' is not a multiple of four. Special-case the glAreTexturesResident() functions now. To fix the bug, we use a temporary buffer that's a multiple of four bytes in length. NOTE: this commit also reverts part of commit 919ec22ecf72aa163e1b97d8c7381002131ed32c (glx/x11: Added some #ifdef GLX_DIRECT_RENDERING protection) which directly edited the indirect.c file rather than the python generator! I'm not repairing that issue at this time.
* mesa: move some glapi bits aroundBrian Paul2008-09-211-0/+3
| | | | | | Move _glapi_proc typedef from glapitable.h to glapi.h Also, don't include glapitable.h from glapi.h Before we were including the huge glapitable.h file in every .c file.
* recreate from changed gl_API.xmlRoland Scheidegger2007-11-091-126/+98
|
* Alias glStencilOpSeparateATI with glStencilOpSeparate.Brian2007-10-301-12/+5
|
* Finish up ATI_separate_stencilBrian2007-10-301-5/+19
| | | | | | Add entrypoints to glapi XML file and regenerate files. Implement glStencilOpSeparateATI(). Consolidate some code in stencil.c
* Initial implementation of MESA_texture_arrayIan Romanick2007-05-161-5/+12
| | | | | Shadow sampling from texture arrays is still not implemented. Everything else should be there, though.
* Added OpenGL 2.1 entrypoints.Brian Paul2006-11-031-343/+385
|
* Update gl_API.xml with OpenGL 2.0 functions, regenerate derived files.Brian Paul2006-11-021-346/+437
|
* Fix bug #4681.Ian Romanick2006-10-111-323/+211
| | | | | | | | | | | | | | | | | glDeleteTextures and glDeleteTexturesEXT were erroneously listed as aliases of each other. For anything /except/ GLX protocol they are aliases. This set of changes allows functions that are functionally identical but have different GLX protocol to be listed as aliases. When building with GLX_INDIRECT_RENDERING set, different static functions are used. These functions determine whether the current context is direct rendering or not. If the context is direct rendering, the aliased function (e.g., glDeleteTextures in the case of glDeleteTexturesEXT) is called. If the context is not direct rendering, the correct GLX protocol is sent. For a deeper explanation of what is changed, please see: http://dri.freedesktop.org/wiki/PartiallyAliasedFunctions
* Changes to generated code caused by the previous commits.Ian Romanick2006-10-041-21/+21
|
* Deprecate GL_EXT_vertex_weighting.Ian Romanick2006-08-291-186/+165
| | | | | | Nvidia no longer supports this extension, and they no longer export its entry points from their libGL. There's no reason for us to keep dragging it around either.
* GL_EXT_paletted_texture functions should alias GL_SGI_color_table functions.Ian Romanick2006-08-241-219/+198
| | | | | | | | | | The functions for GL_EXT_paletted_texture that do not share GLX protocol with GL_ARB_imaging are supposed to alias the similar functions from GL_SGI_color_table. They didn't. This patch corrects this problem and enables GLX protocol for both extensions. Since this removes 3 entries from the dispatch table, this change creates a lot of changes in the generated files.
* Add a new offset mode to the GL API XML. This mode, called "assign,"Ian Romanick2006-08-241-2122/+1772
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | tells the scripts to assign an available offset to the function. The important changes are in src/mesa/glapi/gl_XML.py and src/mesa/glapi/*.xml. Since the DRI drivers only depend on functions required by the ABI (e.g., GL 1.2 + ARB_multitexture) having fixed offsets, all functions not in the ABI use "assign" mode. This has caused the offset of basically every function outside the ABI to change. I have verified that a libGL with this patch works with a DRI driver without the patch. Futher, several function were removed from the dispatch tables altogether. These are the functions for the following extensions: GL_SGIS_texture_filter4 GL_SGIS_texture4D GL_SGIS_detail_texture GL_SGIS_sharpen_texture GL_SGIX_sprite GL_SGIX_instruments GL_SGIX_framezoom GL_SGIX_tag_sample_buffer GL_SGIX_reference_plane GL_SGIX_flush_raster GL_SGIX_list_priority GL_SGIX_fragment_lighting GL_PGI_misc_hints GL_EXT_index_material GL_EXT_index_func GL_3DFX_tbuffer This removes 50 functions from the dispatch table.
* Add support for GL_EXT_gpu_program_parameters. Any driver that enablesIan Romanick2006-08-151-1/+15
| | | | | either GL_ARB_vertex_program or GL_ARB_fragment_program should enable this extension as well.
* Add support for GL_APPLE_vertex_array_object. Several test programsIan Romanick2006-06-121-1/+29
| | | | | | | and demos are also added. Adding basic support to drivers should be as easy as just enabling the extension, though thorough test would also be required.
* Added glBlitFramebufferEXT function.Brian Paul2006-03-011-1/+8
|
* Updates for GL_EXT_timer_query:Brian Paul2005-12-071-1/+15
| | | | | New GLint64EXT and GLuint64EXT types (use C99's long long types). New glGetQueryObject[u]i64vEXT() functions.
* Fix recent problems with display lists and other parts of the code.Ian Romanick2005-08-051-4/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | CALL_by_offset, SET_by_offset, and GET_by_offset all had various problems. The core issue is that parts of the device-independent code in Mesa assumes that all functions have slots in the dispatch table. This is especially true in the display list code. It will merrilly try to set dispatch pointers for glVertexAttrib1fARB even if GL_ARB_vertex_program is not supported. When the GET/SET/CALL macros are invoked, they would read a 0 from the remap table. The problem is that 0 is the dispatch offset for glNewList! One change is that the remap table is now initialized to be full of -1 values. In addtion, all of the *_by_offset marcos misbehave in an obvious way if the specified offset is -1. SET_by_offset will do nothing, GET_by_offset will return NULL, and CALL_by_offset, since it uses GET_by_offset, will segfault. I also had to add GL_EXT_blend_func_separate to the list of default extensions in all_mesa_extensions (src/mesa/drivers/dri/common/utils.c). Even though many drivers do not export this extension, glBlendFunc is internally implemented by calling glBlendFuncSeparate. Without this addition, glBlendFunc stopped working on drivers (such as mga) that do not export GL_EXT_blend_func_separate. There are still a few assertions / crashes in GL_ARB_vertex_program tests, but I don't think that these are related to any of my changes.
* Major rip-up of internal function insertion interface. The oldmesa_6_3_1Ian Romanick2005-07-281-1/+1645
| | | | | | | | | | | | | | | | | | | | | | _glapi_add_entrypoint has been replaced by a new routine called _glapi_add_dispatch. This new routine dynamically assignes dispatch offsets to functions added. This allows IHVs to add support for extension functions that do not have assigned dispatch offsets. It also means that a driver has no idea what offset will be assigned to a function. The vast majority of the changes in this commit account for that. An additional table, driDispatchRemapTable, is added. Functions not in the Linux OpenGL ABI (i.e., anything not in GL 1.2 + ARB_multitexture) has a fixed offset in this new table. The entry in this table specifies the offset in of the function in the real dispatch table. The internal interface was also bumped from version 20050725 to 20050727. This has been tested with various programs in progs/demos on: radeon (Radeon Mobility M6) r128 (Rage 128 Pro) mga (G400)
* Missed this on the previous commit.Ian Romanick2005-07-181-0/+2498
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-28 18:28:46 +0000