this post was submitted on 08 Mar 2025
1473 points (100.0% liked)
linuxmemes
23812 readers
1444 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
3. Post Linux-related content
sudo
in Windows.4. No recent reposts
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
@qqq @OpenStars before wow64 introduction, wine required 32 bit process and multilib to run 32 bit code, requiring 32 bit opengl/bulkan implementations
But it is possible to run 32 bit code in 64 bit process.
Wine in wow64 mode enforces 64 bit process to use only lower 32 bits address space and thunks 64 bit libraries via wine nt syscall interface to loaded 32 bit PE binaries. No multilib or even 32 bit process support required, 32 bit instructions executed as is. Also this allows using machine code translation layers (like fexemu) exposing native calls with same syscall interface.
wow64 maybe still limitted because it does not allow calling native libraries directly and increases overhead. win32 TLS code is using same fs segment register as linux 64bit TLS and workarounds may have bigger overhead, than using multilib