this post was submitted on 16 Jun 2026
20 points (100.0% liked)
Rust
8073 readers
47 users here now
Welcome to the Rust community! This is a place to discuss about the Rust programming language.
Wormhole
Credits
- The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I would expect it to apply to everything. You don't want to hit the issues in the first place.
It seems like a weighing of (safe) CPU support vs better generated instructions. If you don't care about a CPU generation, maybe because it's old enough, or your target environment is restricted/controlled, you don't enable it. If it's still out there and you want to or have to support it, you enable it.
I would imagine a "CPU-Workaround--" or something, and if you enable it, it completely evades the instruction constellations that cause the issues and uses alternatives instead.
Maybe it could have "evade completely" (same code runs on every CPU) and "generate cpu-checked workaround code branches" (faulty CPUs execute a different branch) as alternatives.