Re: glapi_x86.S glx86asm.py

2003-01-30 Thread Dr Andrew C Aitchison
On Thu, 30 Jan 2003, Alexander Stohr wrote: according to its headline glapi_x86.S was generated by the script glx86asm.py - its just that i cannot find that script in the XFree86 sources. Any hints? From CVS/XFree86/xc/extras/Mesa/bin/Attic/glx86asm.py,v revision 1.2 date: 2000/12/07

RE: glapi_x86.S glx86asm.py

2003-01-30 Thread Stuart Anderson
On Thu, 30 Jan 2003, Alexander Stohr wrote: From CVS/XFree86/xc/extras/Mesa/bin/Attic/glx86asm.py,v really? hmm, if the respective API listing ever changes or extends it might be simpler to use an existing script and then submitting the results than to perform error prone copy and paste

Re: glapi_x86.S glx86asm.py

2003-01-30 Thread Ian Romanick
Alexander Stohr wrote: From CVS/XFree86/xc/extras/Mesa/bin/Attic/glx86asm.py,v revision 1.2 date: 2000/12/07 16:12:47; author: dawes; state: dead; lines: +0 -0 Remove from the trunk the Mesa files that aren't needed. Latest entry in cvs log of c/extras/Mesa/src/X86/glapi_x86.S revision 1.7

RE: glapi_x86.S glx86asm.py

2003-01-30 Thread Alexander Stohr
You'd have to ask Brian to be sure, but I believe the intention is that if the interface ever changes, a new .S file be generated in the Mesa tree and imported to the XFree86 DRI trees. There should never be a case where the .S file would change in XFree86 and not change in Mesa.