From 1c62ae0d31b8a68498df16ef5f4a43c8053e88fc Mon Sep 17 00:00:00 2001 From: Simonas Kazlauskas Date: Tue, 20 Aug 2024 10:38:36 +0300 Subject: [PATCH] Do not mandate use of SHA-NI instruction That said, development currently happens on machines with this instruction enabled and our fee structure will assume use of this instruction in the long run, meaning that this instruction will become required to keep up with the network in due time anyway. This also fixes other feature names. I had looked at the LLVM names, rather than Rust ones in the list :facepalm: --- .cargo/config.toml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.cargo/config.toml b/.cargo/config.toml index b9b82d58500..47cbfabf9a3 100644 --- a/.cargo/config.toml +++ b/.cargo/config.toml @@ -4,4 +4,4 @@ rustflags = ["-Cforce-unwind-tables=y"] [target.'cfg(target_arch = "x86_64")'] -rustflags = ["-Ctarget-feature=+sse2,+ssse3,+sse4.1,+sse4.2,+sha,+popcnt,+fma,+bmi,+bmi2,+lzcnt,+movbe,+pclmul,+sahf", "-Cforce-unwind-tables=y"] +rustflags = ["-Ctarget-feature=+sse2,+ssse3,+sse4.1,+sse4.2,+popcnt,+fma,+bmi1,+bmi2,+lzcnt,+movbe,+pclmulqdq", "-Cforce-unwind-tables=y"]