3 ms·
It's never a compiler bug, and it's definitely never a CPU bug. Unless you're a low level kernel developer, then it's both! (Jokes aside, it's still much, muc
by anyfoo 2y ago
It's never a compiler bug, and it's definitely never a CPU bug.
Unless you're a low level kernel developer, then it's both!
(Jokes aside, it's still much, much more often not than it is, but it definitely does happen.)
- mschuster91 2y ago> Unless you're a low level kernel developer, then it's both! Or you're working in cryptography code and have to fight against compilers optimizing away sensitive stuff [1] - or adding junk back in [2]. [1] https://www.redhat.com/en/blog/security-flaws-caused-compiler-optimizations https://www.redhat.com/en/blog/security-flaws-caused-compile... [2] https://pqshield.com/pqshield-plugs-timing-leaks-in-kyber-ml-kem-to-improve-pqc-implementation-maturity/ https://pqshield.com/pqshield-plugs-timing-leaks-in-kyber-ml...