summaryrefslogtreecommitdiffstats
path: root/src/mesa/glapi
Commit message (Collapse)AuthorAgeFilesLines
* remove unneeded HIDDEN definition (bug 4956)Brian Paul2005-11-041-14/+0
|
* implement USE_MGL_NAMESPACE for x86-64 dispatch code (Mark Bolstad)Brian Paul2005-11-021-5/+14
|
* restore FASTCALL stuffBrian Paul2005-10-201-3/+5
|
* Disable the FASTCALL optimization because it still breaks server-side GLX.Brian Paul2005-10-201-5/+3
|
* ifdef out some code to make glapi.c linkable in libglx.so (on theIan Romanick2005-10-111-1/+5
| | | | | server). This isn't strictly needed yet, but it doesn't hurt anything either. However, the patches for fd.o bug #2996 require this to build.
* Add 'get' data for glGetFramebufferAttachmentParameterivEXT enums.Ian Romanick2005-10-102-6/+16
| | | | Remove an extra closing parenthesis in the Linux version of the SWAP_32 macro.
* Change the 'count' for COMPRESSED_TEXTURE_FORMATS from "?" to "-1". ThisIan Romanick2005-10-032-2/+4
| | | | | | | | | | | signals to the script (glX_proto_size.py) that generates the server-side size functions that a handcoded query is needed to determine the data size. Also do s/FOG_COORD_SOURCE/FOG_COORD_SRC/. When initializing the count in glx_enum::__init__, cast the local property to int. Thanks to Python's dynamic typing, if this isn't done the type of stored count will be a string instead of an int.
* Remove the non-existant --get-alias-set option from the help text.Ian Romanick2005-10-031-11/+30
| | | | | | | | | | | | Update printPixelFunction (which is only used to generate code for the server-side) to use the correct method for obtaining the dimensions of the image parameter to a function. Only use byteswap.h when building generated code on Linux. Elsewhere use the (horrible!) macros from X11/misc.h. Make sure that enums associated with the generic "Get" function get applied to GetIntegerv, GetBooleanv, GetFloatv, and GetDoublev.
* Committing in .Jouk Jansen2005-09-231-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | 1) change compilation on VMS to use IEEE floating points 2) one more problem with _mesa_sprintf solved Modified Files: Mesa/docs/README.VMS Mesa/progs/demos/descrip.mms Mesa/progs/tests/descrip.mms Mesa/progs/util/descrip.mms Mesa/progs/xdemos/descrip.mms Mesa/src/glu/mesa/descrip.mms Mesa/src/glu/sgi/descrip.mms Mesa/src/glut/glx/descrip.mms Mesa/src/mesa/array_cache/descrip.mms Mesa/src/mesa/drivers/common/descrip.mms Mesa/src/mesa/drivers/osmesa/descrip.mms Mesa/src/mesa/drivers/x11/descrip.mms Mesa/src/mesa/glapi/descrip.mms Mesa/src/mesa/main/descrip.mms Mesa/src/mesa/main/texobj.c Mesa/src/mesa/math/descrip.mms Mesa/src/mesa/shader/descrip.mms Mesa/src/mesa/shader/grammar/descrip.mms Mesa/src/mesa/shader/slang/descrip.mms Mesa/src/mesa/swrast/descrip.mms Mesa/src/mesa/swrast_setup/descrip.mms Mesa/src/mesa/tnl/descrip.mms ----------------------------------------------------------------------
* remove _swrast_DrawBufferKarl Schultz2005-09-051-2/+1
|
* /dri/msgAdam Jackson2005-08-262-2/+2
|
* Fix the scripts for the cygwin & mingw changesAlan Hourihane2005-08-262-2/+8
|
* Remove the logic that determines at compile time whether or not HAVE_ALIASIan Romanick2005-08-112-21/+0
| | | | | | | | should be defined. It was flawed on some platforms (e.g., Darwin & mingw). Instead, rely on the build system to define it on the compiler command line. This also reverts ajax's hand-edit to indirect_size.c. I'll fix that on the X.org side of things later today.
* Remove _glapi_check_multithread from the interface exported by the loader toIan Romanick2005-08-105-286/+62
| | | | | | | | | | | | | | | | | the driver. The loader now takes care of this for the driver. Remove _glapi_DispatchTSD and give _glapi_Dispatch its semantic (i.e., having a NULL value means that the application is multithreaded and _glapi_get_dispatch must be called). Gut all of the dispatch override code. This removes _glapi_RealDispatch, _glapi_tls_RealDispatch, _glapi_begin_dispatch_override, _glapi_end_dispatch_override, and _glapi_get_override_dispatch. Remove _glapi_get_proc_address, _glapi_get_proc_name, _glapi_get_version, and _glapi_check_table from the loader / driver interface. Reviewed by: Brian Paul
* Add rules and target to build src/mesa/x86-64/glapi_x86-64.S.Ian Romanick2005-08-091-0/+4
|
* s/Disaptch/Dispatch/ (bug 3918)Brian Paul2005-08-081-1/+1
|
* Fix recent problems with display lists and other parts of the code.Ian Romanick2005-08-054-9/+475
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* Convert all instances of XTHREADS to USE_XTHREADS. This fixes one ofIan Romanick2005-08-034-6/+6
| | | | | serveral things that are broken when building on a system with X.org 7.0rc0 installed.
* Major rip-up of internal function insertion interface. The oldmesa_6_3_1Ian Romanick2005-07-288-116/+1939
| | | | | | | | | | | | | | | | | | | | | | _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)
* Fix SPARC assembly for 64-bitIan Romanick2005-07-282-21/+22
| | | | | | | | | | | | | | - The test for whether or not we're building for 64-bit is '#ifdef __arch64__'. This appears to be correct on both Linux and Solaris. - The test for Solaris is now '#if defined(SVR4) || defined(__SVR4) || defined(__svr4__)'. GCC 3.4.0 has all three defined on Solaris 9. - Enables assembly language clip routines. - Fixes to make GLSL code build on Solaris. - Update gl_SPARC_asm.py.
* Missed this on the previous commit.Ian Romanick2005-07-181-0/+2498
|
* Wrap every place that accesses a dispatch table with a macro. A new script-Ian Romanick2005-07-183-12/+102
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | generated file, called src/mesa/glapi/dispatch.h, is added. This file contains three macros for each API function. It contains a GET, a SET, and a CALL. Each of the macros take a pointer to the context and a pointer to the dispatch table. In several threads on mesa3d-dev we discussed replacing _glapi_add_entrypoint with a new function called _glapi_add_dispatch. For this discussion, the important difference between the two is that the caller of _glapi_add_dispatch does *not* know what the dispatch offset will be at compile time. Because of this callers need to track the dispatch offset returned by _glapi_add_dispatch. http://marc.theaimsgroup.com/?t=111947074700001&r=1&w=2 The downside is that driver code then has to access the dispatch table two different ways. It accesses it using structure tags (e.g., exec->Begin) for functions with fixed offsets and via a remap table (e.g., exec[ remap->NewExtensionFunction ]) for functions without fixed offsets. Yuck! Using the macros allows both types of functions to be accessed identically. If a driver needs to set a pointer for Begin, it does 'SET_Begin(ctx, exec, my_begin_function)'. If it needs to set a pointer for NewExtensionFunction, it does 'SET_NewExtensionFunction(ctx, exec, my_NewExtensionFunction_function)'. Furthermore, if at some point in the future a static offset is assigned for NewExtensionFunction, only the macros need to change (instead of every single place that accesses a table for that function). This code differs slightly from the originally posted patches in that the CALL, GET, and SET marcos no longer take a context pointer as a parameter. Brian Paul had suggested that the remap table could be stored as a global since it would be set at CreateScreen time and would be constant for all contexts. This change reflects that feedback. http://marc.theaimsgroup.com/?t=112087194700001&r=1&w=2
* Add support for assembly (static) dispatch functions on x86-64. ThisIan Romanick2005-07-022-4/+314
| | | | | | is basically patch #2939 from X.org bugzilla #3379. This does *not* fix the bug as it does not dynamically generate stubs at run-time. It just gets things one step closer.
* Move the PYTHON2 and PYTHON_FLAGS assignments to configs/current, andBrian Paul2005-07-011-3/+3
| | | | | include $(TOP)/configs/current in glapi/Makefile so those vars can be easily overridden by any system config, if needed.
* Replace add_newer_entrypoints (src/mesa/main/context.c) withIan Romanick2005-06-302-0/+293
| | | | | | | | | | | | | | | device-specific code. A new Python script (src/mesa/glapi/extension_helper.py) generates a list of all entry-points for all known extensions. Each driver the selects only the extensions that it needs and enables the via either driInitExtensions or driInitSingleExtension. This code has been compile-tested on a drivers, but has only been run-tested on mga and i915 (on i830 hardware). These changes were discussed at length on the mesa3d-dev mailing list. http://marc.theaimsgroup.com/?t=111947074700001&r=1&w=2
* Ignore files generated as part of the build process.Ian Romanick2005-06-241-0/+11
|
* Fix non-x86 specific builds. The changes from glTexImage3DEXT toIan Romanick2005-06-245-109/+117
| | | | | | | | | | | | | | | glTexImage3D that caused me so many problems during the re-development of the API scripts reared its ugly head again. This has been fixed by tracking the parameter string for each entry-point individually. This has the annoying side-effect that the names of the parameters in all aliases of a function must be the same or gl_apitemp.py will generate bad code. :( The changes in src/mesa/glapi/{gl_API.xml,glapitable.h} and src/glx/x11/* are caused by fixing the parameter names in various function aliases that didn't match. Reported by: Eric Anholt, Jacob Jansen
* Fixed the XCB implementation when always_array is true, thanks to Ian ↵Jeremy Kolb2005-06-241-1/+2
| | | | Romanick for pointing it out. Please review.
* Mark GenQueriesARB at 'always_array="true"'. This eliminates the needIan Romanick2005-06-222-2/+2
| | | | to special-case the handling of that function in glX_proto_send.py.
* Fixed a bug where GenQueriesARB was generating the wrong code for XCB and ↵Jeremy Kolb2005-06-221-1/+1
| | | | wouldn't compile. Not sure how that slipped through before but it should work now.
* Mammoth update to the Python code generator scripts that live inIan Romanick2005-06-2119-3448/+3832
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | src/mesa/glapi. Basically, the scripts that did simple things (like gl_offsets.py) were simple, and the scripts that did more complicated things (like glX_proto_send.py) were getting progressively more and more out of control. So, I re-write the foundation classes on which everything is based. One problem with the existing code is that the division between the GL API database representation and the way the output code is generated was either blury or nonexistant. The new code somewhat follows the Model-View-Controller pattern, minus the Controller. There is a distinct set of classes that model the API data, and there is a distinct set of classes that generate code from that data. One big change is in the class that represents GL functions (was glFunction, is now gl_function). There used to be an instance of this calls for each function and for each alias to that function. For example, there was an instance for PointParameterivSGIS, PointParameterivEXT, PointParameterivARB, and PointParameteriv. In the new code, there is one instance. Each instance has a list of entrypoint names for the function. In the next revision, this will allow a couple useful things. The script will be able to verify that the parameters, return type, and GLX protocol for a function and all it's aliases match. It will also allow aliases to be represented in the XML more compactly. Instead of repeating all the information, an alias can be listed as: <function name="PointParameterivARB" alias="PointParameterivEXT"/> Because the data representation was changed, the order that the alias functions are processed by the scripts also changed. This accounts for at least 2,700 of the ~3,600 lines of diffs in the generated code. Most of the remaining ~900 lines of diffs are the result of bugs *fixed* by the new scripts. The old scripts also generated code with some bugs in it. These bugs were discovered while the new code was being written. These changes were discussed on the mesa3d-dev mailing list back at the end of May: http://marc.theaimsgroup.com/?t=111714569000004&r=1&w=2 Xorg bug: 3197, 3208
* ran "make" after update to glX_proto_send.py.Jeremy Kolb2005-06-201-397/+397
|
* Fixed some issues where XCB replies were being freed and data was not being ↵Jeremy Kolb2005-06-201-4/+2
| | | | copied.
* Fix gl_enums.py so that enums that are listed with the same name inIan Romanick2005-05-261-2/+9
| | | | multiple places don't get generated multiple times.
* Minor correction to EXT_framebuffer_object XML. Fix gl_table.py so that itIan Romanick2005-05-264-7/+7
| | | | generates the correct script name in the generated output.
* Make a couple minor corrections to gl_API.xml. Fixes the name of anIan Romanick2005-05-263-11/+11
| | | | | | | | extension that was missing the GL_ part and uses the core GL type names for vertex buffer object functions instead of the ARB names. Also commits the resulting changes to the generated code. Some how, the #if sequence disappeared in the 1.52 version of glapi_x86.S.
* Fix a couple typeos in enum names.Ian Romanick2005-05-251-2/+2
|
* moved to windows build dirKarl Schultz2005-05-241-124/+0
|
* another GLX / XCB patch (Jeremy Kolb)Brian Paul2005-05-161-4/+4
|
* Patches for XCB (Jeremy Kolb)Brian Paul2005-05-071-5/+60
|
* Stop gcc-4.0 complaining about "type qualifiers ignored on functionKeith Whitwell2005-04-281-1/+1
| | | | return type".
* Stop gcc-4.0 complaining about "type qualifiers ignored on functionKeith Whitwell2005-04-281-1/+1
| | | | return type".
* If the file name passed to parse_GL_API is None or "-", read from standardIan Romanick2005-04-181-1/+7
| | | | input. This allows use of GL API scripts in pipelines.
* Refactor a bunch of common code from the "leaf" scripts to a new functions,Ian Romanick2005-04-1812-141/+29
| | | | parse_GL_API, in gl_XML.py.
* Fill-in function offsets and correct a couple typos.Ian Romanick2005-04-181-25/+28
|
* Convert all Python scripts to use XML namespaces.Ian Romanick2005-04-1812-92/+106
|
* Move the DTD to its own file.Ian Romanick2005-04-182-122/+121
|
* Reverted the last change back to fix bug 3035Ben Crossman2005-04-151-1/+1
|
* Convert 'variable_param' from a CDATA attribute to a NMTOKENS attribute.Ian Romanick2005-04-142-5/+5
| | | | | The main difference is that white-space is used to separate the names instead of comas.
* Refactor the handling of the '(true | false)' enumerated attributes.Ian Romanick2005-04-142-54/+27
|
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-11 23:31:24 +0000