[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wine-devel
Subject:    Re: Wine configurations naming
From:       Zebediah Figura <zfigura () codeweavers ! com>
Date:       2023-03-31 19:02:51
Message-ID: 5ece4e99-ef31-9d28-51af-9f3d5db799b9 () codeweavers ! com
[Download RAW message or body]

On 3/31/23 12:47, Gabriel Ivăncescu wrote:
> On 31/03/2023 19:59, Zeb Figura wrote:
>> On 3/31/23 11:46, Eric Pouech wrote:
>>> So this mail to share the question, and a proposal
>>>
>>> - *wow64*: the new multi-arch wow64 configuration, which mimics 
>>> windows wow64 architecture ; dropping the 'new' to match with windows 
>>> (and also, not sure that in 10years from now it will still be "new")
>>
>> I don't see what is gained by being *less* specific, especially when 
>> we've been referring to this as unqualified "wow64" for years. I fully 
>> intend to keep calling this "new", and I'd exhort anyone else to as well.
>>
>>
> 
> Isn't the "old wow64" still going to be used if the host supplies the 
> necessary 32-bit libraries? To avoid rather expensive syscalls and mode 
> switches (only "unix calls"). I recall something along those lines.

I would have thought so, but apparently we've started making some 
features exclusive to new-style wow64. (Note that syscalls happen either 
way, but mode switches are definitely going to be expensive.)



[prev in list] [next in list] [prev in thread] [next in thread]