Hacker News Reader

ptitSebon New Box64 v0.3.2 and Box86 v0.3.8 released (Native Flags, Benchmarks, Box32)

you don't like my title?

ptitSebon New Box64 v0.3.2 and Box86 v0.3.8 released (Native Flags, Benchmarks, Box32)

I tried to fix the typo. It should be better now. And yeah, Box86/Box64 let you run x86 linux programs on non-x86 platforms, like Rosetta on macOS.

ptitSebon New Box64 v0.3.2 and Box86 v0.3.8 released (Native Flags, Benchmarks, Box32)

Thanks for the tip, I'll try to keep that in mind next time :)

ptitSebon New Box64 v0.3.2 and Box86 v0.3.8 released

New releases, with some benchmarks acrosse previous version and vs Rosetta. Also introducing Box32 to run 32bits apps on 64bits systems

ptitSebon Box64 and RISC-V in 2024: What It Takes to Run the Witcher 3 on RISC-V

Actually, Box64 can also store operands for later computation, depending on what comes next...

ptitSebon Box64 and RISC-V in 2024: What It Takes to Run the Witcher 3 on RISC-V

No, it's Box64, a completly different project.

(But I do remember the time I had an Amstrad PC1512 too :D )

ptitSebon Box64 and RISC-V in 2024: What It Takes to Run the Witcher 3 on RISC-V

The milk-v pioneer comes with 128GB of RAM.

ptitSebon New box86 v0.3.2 and Box64 v0.2.4 released – RISC-V and WoW64 support

New version of Box86 and Box64 out. Box64 now support RISC-V Dynarec. Also support 32bits proces in experimental Wine WoW64.

ptitSebon Box64 and RISC-V

Dynarec can optionnaly handle Strong Memory Model emulation, but it's disable by default to have maximum emulation speed (it's the BOX86_DYNAREC_STRONGMEM env. var.).

ptitSebon Box64 and RISC-V

The presence of Zba and Zbb extension is tested before using it.

ptitSebon Box64 and RISC-V

Yes, it would be more efficiant, but it will also be more costly to generate. It would also render the handling of Signal more tricky (need to always be able to go back from the RV64 address to the orignial x86_64 address in case of a SEGFAULT for example). Also, intra-block jump make this more complicated. Box64 does a limited full-block optimisation for the Flags handling and SSE/x87/MMX register attribution, but that's pretty much. Some constant propagation mecanism would be nice and could save a lot of opcode, but no worked as been done it that direction for now (maybe later, it always bother me when I look at generated code dump to see also those multiple constant assigned multiple time).

ptitSebon Box64 and RISC-V

I was a bit doubtfull of that claim about RV64 code compacity compared to x86_64, so I tried myself. I used 2 of projects https://github.com/ptitSeb/stuntcarremake and https://github.com/ptitSeb/hydracastlelabyrinth.git and I built them with default option, in release mode on both RV64 and x86_64 to compare the generated file size. For StuntCarRemake: RV64: 191248 x86_64: 260616 For HydraCastleLabyrinth: RV64: 652984 x86_64: 693312

And yeah, RV64 is indeed more compact than x86_64!

ptitSebon Wasmer 3.2.0 released, with RISC-V support

Wasmer 3.2.0 has just been release, and among other thing, there is now support RISC-V, and also WCGI.