Re: RFC: OpenAL Winmm driver and OpenAL32.dll thunk was Re:OpenALand DirectSound

2006-11-23 Thread Stefan Dösinger 
Am Donnerstag 23 November 2006 01:16 schrieb Nick Burns:
> Good point in some cases we can just let get proc address pipe the func ptr
> directly back to the app..
>
> But..
> On Mac OSX -- the stack must be 16 byte aligned (for and lib/sys call) --
> this means we need to thunk for the stack on Max OSX -- If Linux or other
> plats have similar reqs then the thunking is required.
>
> Personally I would rather have the layer as it gives us control on how
> windows talks with the system.
Yeah, I guess modern CPUs make such calls cheap, thanks to all the little 
getters and setters they have to deal with thanks to object oriented 
programming

And we get traces this way


pgpwp7uAVnlbs.pgp
Description: PGP signature

Re: RFC: OpenAL Winmm driver and OpenAL32.dll thunk was Re:OpenALand DirectSound

2006-11-22 Thread Nick Burns 
Good point in some cases we can just let get proc address pipe the func ptr 
directly back to the app..


But..
On Mac OSX -- the stack must be 16 byte aligned (for and lib/sys call) -- 
this means we need to thunk for the stack on Max OSX -- If Linux or other 
plats have similar reqs then the thunking is required.


Personally I would rather have the layer as it gives us control on how 
windows talks with the system.


- Nick


From: Stefan Dösinger <[EMAIL PROTECTED]>
To: wine-devel@winehq.org
Subject: Re: RFC: OpenAL Winmm driver and OpenAL32.dll thunk was 
Re:OpenALand DirectSound

Date: Wed, 22 Nov 2006 12:38:46 +0100

Hi,
> That being said -- the impls for AL_1_0, ALC_1_0, ALUT (not freealut) --
> are as good as they can be. They are straight shots thru to the api
> (bouncing
>
> >from CDECL(win32) -> ???(host???))
Afaik Linux libs are CDECL, if the win32 openal is CDECL too(not WINAPI /
STDCALL), can we pass the Linux function pointers directly to the apps?
Wasn't there some .so loading in the wine library loader some time ago?




<< attach4 >>