-
Notifications
You must be signed in to change notification settings - Fork 107
Panic at llvm.x86.sha1rnds4 #1453
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This comes from using SHA-1. The SHA-256 intrinsics are already implemented. I will implement the SHA-1 intrinsics, but be aware that SHA-1 hash collisions have been demonstrated. |
Could you test the sha1 branch? Prebuilt artifacts should be available at https://github.com/rust-lang/rustc_codegen_cranelift/actions/runs/7716798292 in a couple of minutes. The machine I'm testing on doesn't seem to have support for the sha1 instructions. |
Indeed, I see sha-1 is transitive dependency in latest version of web3 crate that we use.
Thanks for such quick response and let me know if there's anything else I can help with. BTW I see your |
Should be fixed now. Precompiled artifacts available at https://github.com/rust-lang/rustc_codegen_cranelift/actions/runs/7739824014 |
It works, thanks! Any ETA when we could expect this in nightly? |
Thanks for confirming it works! I've merged that branch into the master branch of this repo. I don't have an ETA for when I will do the next sync into the rust repo yet. It will be available on the next nightly after I've done a sync. I will let you know when that happens. |
The sync was done earlier today. It will be in the next nightly. |
Error:
looks like due sha2 crate usage. Should be related to #1173 and #1427.
Let me know if any additional info is required, cheers
The text was updated successfully, but these errors were encountered: