immunity to security vulnerabilities in AVX512 code by not actually supporting running AVX512 code
haha *sweats* SSSE3 ought to be enough for anybody
immunity to security vulnerabilities in AVX512 code by not actually supporting running AVX512 code
haha *sweats* SSSE3 ought to be enough for anybody
@guenther I'm not an expert on this topic but I believe a brief explanation is that it's the operating system's job to save and restore hardware registers, and AVX-512 added a new set of hardware registers.
Here are some relevant Problem Reports.
https://gnats.netbsd.org/59860
https://gnats.netbsd.org/60426
@argv_minus_one @koorogi @guenther
you just invented XSAVE. unfortunately however it was designed by intel
@ltning Aren't there like a whole bunch of netbsd ports that are softfp
@ltning x86 is legacy. come back when it's an architecture that matters, like vax or m68k
@techokami @netbsd @ltning Only PA-RISC has a future, and possibly Itanium.
All the others are going to fail.
@thomholwerda @techokami @ltning Even we don't care about Itanic. SPARC on the other hand you will pry from my cold dead hands.
Anything made by intel is obviously legacy compared to say, big endian arm64
@netbsd @techokami @ltning This Itanium slander shall not be forgotten.
@techokami @netbsd @ltning more lies and slander
i will not stand for it
@thomholwerda @netbsd @ltning As I said at the end of that piece, "This was a CPU that had a lot of promise, but instead suffered numerous technical issues, massive delays, shunned by half of its family, and was never able to properly take advantage of all that it could do. This is just sad."
@netbsd Why would a binary on NetBSD need any sort of operating system support to call avx instructions?