2 ms·
I’m not even sure what that would mean. A compiler is a compiler, regardless if it’s Intel making it or not. They’re the exact same thing as if you used clang.
by steveklabnik 7y ago
I’m not even sure what that would mean. A compiler is a compiler, regardless if it’s Intel making it or not.
They’re the exact same thing as if you used clang.
(It’s only relevant because you seem to imply that Intel doesn’t care about Rust at all. That’s not true.)
- Const-me 7y ago> They’re the exact same thing as if you used clang. Are you sure functions calls that crate adds on top of every single instruction, transmute(), as_i32x4(), etc., compile into nothing? And do so reliably i.e. every single time regardless on the surrounding code? BTW, functions built on top of intrinsics aren’t reliable in clang. I sometimes have to use compiler-specific trickery to force compilers to inline stuff, keep data in registers instead of loads/stores, and otherwise not screw up the performance.
- steveklabnik 7y agoIn my understanding, if it does not, that’s a bug. Compiler bugs do happen. Sounds like you’ve hit a few with clang.