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 did not expect any reference to LLVM when using cranelift. Is this library depending on some instruction that exists within LLVM? Have I mis-configured something?
I found this related issue which is why I'm asking those questions:
Feel free to close if this is considered spam or if I need to ask the folks in the cranelift repository anything. I just don't know how to proceed so thought I would ask here first. Thank you for your time.
The text was updated successfully, but these errors were encountered:
You might want to report this to cranelift. It's another missing x86 intrinsic which needs an inline ASM implementation, similar to rust-lang/rustc_codegen_cranelift#1425
llvm.x86.avx2.permd looks correct, although it's probably not the only one which needs to be implemented for the poly1305 AVX2 backend to work.
I believe setting the poly1305_force_soft cfg attribute will disable AVX2 support. Alternatively if there's some way to detect cranelift we can at least temporarily disable the AVX2 backend when compiling there.
Hi there,
I've created a super-minimal repository that reproduces the problem I'm running into:
https://github.com/dimitri-lenkov/cranelift_aead
Basically I'm seeing the following error while running tests. The text
llvm.x86.avx2.permd
(at the very end) caught my eye.I did not expect any reference to LLVM when using cranelift. Is this library depending on some instruction that exists within LLVM? Have I mis-configured something?
I found this related issue which is why I'm asking those questions:
RustCrypto/block-ciphers#391
Feel free to close if this is considered spam or if I need to ask the folks in the cranelift repository anything. I just don't know how to proceed so thought I would ask here first. Thank you for your time.
The text was updated successfully, but these errors were encountered: