The technique we were using to disable SSE2 in the standard library turned It took us a while to recognize that we could not just disable SSE2 because, In short, you cannot use the -sse2 flag with Rust. With IEEE floating point disabled, LLVM attempts to use the old 80-bit x87 floating point unit and thenįails an assertion while compiling your code. Ctarget-feature=-sse2 flag turns of both SSE2 vector instructions and Instructions without breaking floating point. Work is that it is not possible to turn off the x86 architecture’s SSE2 The reason that telling the compiler not to use vector instructions does not Will need to modify the C code’s build system – which is a bit more work.)

(If your program calls C code that was not compiled using the CC-rs crate, you Then you can easily pass flags to the C compiler to disable auto-vectorization.

Uses a crate that calls C code) and uses the CC-rs crate to compile the code,

RUSTFLAGS if you are using rustc directly, you can directly disableĪuto-vectorization when invoking rustc. If you are using cargo, you can control this with The first of these ideas probably works: you can tell the compiler not toĪuto-vectorize code. Unfortunately, two of those three ideas don’t work – but we think we have a Not to use vector instructions and use existing conditional compilationįeature flags to disable hand-vectorized code. Research is characterized by allowing yourself to make mistakes: performingĮxperiments drawing conclusions later, realizing that yourĮxperiment was not sufficient and you got it wrong andīack in March, we thought that we knew how to deal with vectorized Rust: tell the compiler not to auto-vectorize code tell the compiler

Rust mobile no verification