You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I know that each function has a set of preconditions, it would be great if we can easily check for those at run time (instead of rolling our own custom checkers). E.g., AES key expansion adapts to AVX or SSE. However, it also requires AES. Ran into a setup which used Haswell but with AES-NI disabled in BIOS (not sure why this is still the default with certain vendors). Got an illegal instruction error. Thanks
The text was updated successfully, but these errors were encountered:
Almost all functions in the library have base functions that are highly portable and few minimum requirements so the multi-binary interface has few restrictions. The block ciphers in isa-l_crypto are one exception to this and do require AES-NI as a minimum.
Some early CRB boards have AES-NI disabled in BIOS but do re-enable for production boards.
I have bumped into this issue as well - somebody run Java JNI wrapper for isa-l_crypto I wrote on computer without AES instructions. That ended ugly with Java core dump. I will need to write check for AES support. If there would be something simple like that added to isa-l_crypto, I would use it for sure.
I know that each function has a set of preconditions, it would be great if we can easily check for those at run time (instead of rolling our own custom checkers). E.g., AES key expansion adapts to AVX or SSE. However, it also requires AES. Ran into a setup which used Haswell but with AES-NI disabled in BIOS (not sure why this is still the default with certain vendors). Got an illegal instruction error. Thanks
The text was updated successfully, but these errors were encountered: