Re: [Mesa3d-dev] Dispatch generation for x86-64

2006-08-15 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ian Romanick wrote: > Here is my first pass at run-time dispatch generation code for x86-64. > It's not particularly well tested yet (or I'd just commit it now). I > wrote a test program that called fill_in_entrypoint with a few different > parameter

Re: [Mesa3d-dev] Dispatch generation for x86-64

2006-08-14 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brian Paul wrote: > I sometimes wonder if all this complexity to handle dynamic addition of > entrypoints is worth it. It would all be a heck of a lot simpler if we > just updated libGL with the newest entrypoints from time to time and > asked people

Re: [Mesa3d-dev] Dispatch generation for x86-64

2006-08-14 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Keith Whitwell wrote: > Ian Romanick wrote: >> >> There is one catch, and I'm not sure how to resolve it. When a driver >> requests a function, it can request a set of identical functions with >> different names. For example, the driver can request t

Re: [Mesa3d-dev] Dispatch generation for x86-64

2006-08-14 Thread Brian Paul
Ian Romanick wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Ian Romanick wrote: > > >>Normally when an application calls glXGetProcAddress a dummy stub is >>created. In the current implementation, a dispatch offset is not >>assigned at this time. The existing code expects that th

Re: [Mesa3d-dev] Dispatch generation for x86-64

2006-08-14 Thread Keith Whitwell
Ian Romanick wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Ian Romanick wrote: > >> Normally when an application calls glXGetProcAddress a dummy stub is >> created. In the current implementation, a dispatch offset is not >> assigned at this time. The existing code expects that th

Re: [Mesa3d-dev] Dispatch generation for x86-64

2006-08-14 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ian Romanick wrote: > Normally when an application calls glXGetProcAddress a dummy stub is > created. In the current implementation, a dispatch offset is not > assigned at this time. The existing code expects that the driver will > later ask for the

Re: [Mesa3d-dev] Dispatch generation for x86-64

2006-07-04 Thread Keith Whitwell
Ian Romanick wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Here is my first pass at run-time dispatch generation code for x86-64. > It's not particularly well tested yet (or I'd just commit it now). I > wrote a test program that called fill_in_entrypoint with a few different > par

Re: [Mesa3d-dev] Dispatch generation for x86-64

2006-07-04 Thread Nicholas Miell
On Mon, 03 Jul 2006 18:59:24 -0700, Ian Romanick wrote: > Here is my first pass at run-time dispatch generation code for x86-64. > It's not particularly well tested yet (or I'd just commit it now). I > wrote a test program that called fill_in_entrypoint with a few different > parameter signature

[Mesa3d-dev] Dispatch generation for x86-64

2006-07-03 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Here is my first pass at run-time dispatch generation code for x86-64. It's not particularly well tested yet (or I'd just commit it now). I wrote a test program that called fill_in_entrypoint with a few different parameter signature strings, and I ve