Re:Why Is SQLite Coded in C? (2017)
by steveklabnik on Friday March 16, 2018 @10:48AM
(#16601024)
The biggest differences there are due to lack of SIMD. We expect it to be stable quite soon, and that should close the gap quite a bit.
Do you say that because you have coded those programs using SIMD and rustc nightly, and seen that using SIMD eliminates the performance difference ?
Re:Why Is SQLite Coded in C? (2017)
by steveklabnik on Sunday March 18, 2018 @01:06PM
(#16612904)
I have not personally done this, but the people who have identified that as the issue, and what we’re stabilizing is the exact same thing as what C and C++ compilers have, so there’s no reason to believe it would be different. Once it’s stable, we’ll all see!
Someone has repeatedly commented on /r/rust/ that differences are due not so much to SIMD but iirc to not triggering the same LLVM loop unrolling.
Re:Why Is SQLite Coded in C? (2017)
by steveklabnik on Wednesday March 21, 2018 @03:52PM
(#16641700)
I think you're confusing loop unrolling and autovectorization. That said, it's kinda moot, once SIMD is stable, we'll find out :)
>> I think you're confusing loop unrolling and autovectorization. <<
Here's exactly what I was told -- "This was achieved by manually unrolling a 10-step loop, which compiler apparently could not optimize."
Re:Why Is SQLite Coded in C? (2017)
by irundebian on Friday March 16, 2018 @05:19PM
(#16604107)
I would say C will never be as safe as Rust. Just accept it, C is crap. It's just not cool.
http://benchmarksgame.alioth.debian.org/u64q/rust.html