stdarch VS mastermind

Good to know! How would you compare it with the std_detect implementation, underlying the standard library (https://github.com/rust-lang/stdarch/tree/master/crates/std_detect)?

Fortunately, @burntsushi (thanks) is sharing the workaround in the rust-lang github issue. The trick is to reinterpret a (non-tagged) union for this.

The stdarch tests will test target-specific stuff like SIMD while to UI tests are more generic. They both test that the compiler will produce an executable that produce the correct output (or that rustc itself will produce the correct output).

I made enough progress to be able to compile the tests of stdarch and most of them pass: that's a huge milestone!

You can check the code. Apparently the std implementation uses the OSXSAVE register to check that the OS supports saving AVX/AVX2 registers during context switches and only then enables it. In a non-std context one might not generally be able to depend on the OSXSAVE register.

Mastermind intrigued me in the same way as the author some time ago, and I've used it as a standard problem when trying out new computational frameworks/methods ever since.

Here is my Rust version with multi-threading, SIMD, WASM running on your device inside a WebApp: https://0xbe7a.github.io/mastermind/

Repo: https://github.com/0xbe7a/mastermind

It is quite fast (1839202304 position pairs evaluated in 1652ms on my device) and can also exploit some symmetries inside the solution space.