> > Note that if you layout the call structure _exactly_ the same > > way as the stack layout (which is fixed for all Windows API > functions). > > You will get an even faster call mechanism that you currently have. > > Just load a register with the call id another with the offset:ed > > stack pointer and then sys call. > > > > I wonder how many percent faster that will be? > > Out of interest, did you get this idea from looking at the > source code I sent > out earlier? It's changed since then... I'll have to > distribute my revised > stuff tomorrow. Yes. I got the idea as soon as I saw your code. AFAICS it is an obvious optimization.
- Re: RFC - Winelib constructor... Gavriel State
- Re: RFC - Winelib constructor... Alexandre Julliard
- Re: RFC - Winelib constructor... David Howells
- Re: RFC - Winelib constructor... Alexandre Julliard
- Re: RFC - Winelib constructor... David Howells
- Re: RFC - Winelib constructor... Alexandre Julliard
- RE: RFC - Winelib constructor init problem Patrik Stridvall
- Re: RFC - Winelib constructor init problem David Welch
- Re: RFC - Winelib constructor init problem David Howells
- Re: RFC - Winelib constructor init problem David Howells
- RE: RFC - Winelib constructor init problem Patrik Stridvall
- RE: RFC - Winelib constructor init problem Patrik Stridvall
- Re: RFC - Winelib constructor init problem David Howells
- RE: RFC - Winelib constructor init problem Patrik Stridvall
- Re: RFC - Winelib constructor init problem Alexandre Julliard
- Re: RFC - Winelib constructor init problem David Howells
- RE: RFC - Winelib constructor init problem Patrik Stridvall
- Re: RFC - Winelib constructor init problem David Howells
- Re: RFC - Winelib constructor init problem David Howells
- Re: RFC - Winelib constructor init problem Jim Aston
- Re: RFC - Winelib constructor init problem Alexandre Julliard