4 Followers
36 Following
70 Posts
@fclc @linux_mclinuxface and ZFS out of the box (yes I know Ubuntu also has it)
@shac Midori?
@fclc is it more that while Amdahl puts an upper limit on the scaling, you can run different problems in parallel? For example for software video encoding, the higher quality presets reduce parallelism (among other things) to improve quality. However, you can encode multiple videos in parallel to improve utilization?
@fclc Thanks! Yeah RVA23 doesn't currently mandate zacas. The main reason I ask is that 128-bit atomics is really nice to deal with the ABA problem
@fclc Do tenstorrent RISC-V processors support zacas extension? Based on RVA23, it apparently will become mandatory in future profiles.
@never_released @fclc looks like widespread SME support in Macs are going to take a while
@never_released when you don't have enough honesty, you use 4xMultiClaimGen
@never_released Is my understanding of the Apple armv8 versions correct?
A10: compiler states it is 8.1, but it is 8.0 because it lacks lse
A11: v8.2
A12: v8.3
A13: v8.4
A14: v8.4 (missing BTI)
A15: v8.6
A16: v8.6
A17: v8.6
A18: v9.0 (but v8.7 for compiler due to not supporting SVE?)
(though EU devices may get other browser engines). In addition, 32-bit WASM could be faster due to guard pages reducing sandboxing overhead. See https://spidermonkey.dev/blog/2025/01/15/is-memory64-actually-worth-using.html
Is Memory64 actually worth using?

After many long years, the Memory64 proposal for WebAssembly has finally been released in both Firefox 134 and Chrome 133. In short, this proposal adds 64-bit pointers to WebAssembly.

SpiderMonkey JavaScript/WebAssembly Engine
FreeBSD 14 drops support in November 2028. That's not to say it is the end of 32-bit as a whole. Armv7 is still supported in Ubuntu, FreeBSD (as Tier-2), Debian, and Android. RISCV 32-bit is going to be new but most distros and FreeBSD will only support 64-bit. Same for Android. WASM was 32-bit only but Memory64 was approved and shipping in both FireFox and Chrome. Safari will pose a problem however due to it not supporting it yet and that iOS devices are stuck with WebKit