Security code must be correct above all else. Too-clever tricks for tiny performance gains that interfere with readability are the polar opposite of what an SS

Security code must be correct above all else. Too-clever tricks for tiny performance gains that interfere with readability are the polar opposite of what an SSL library ought to be doing. Such libraries ought to never trust compilers because compilers are ever changing, untrusted things. The right approach is clear readable high level code interspersed with inline assembly for critical sections such as constant-time operations. Speaking of which: OpenSSL did that wrong too. They merged some AES NI optimisations without having the CPUs to test it on. This lead to the one and only crash I’ve ever experienced due to a CPU upgrade! Stop justifying what is clearly a trash fire.