Const-me/MemoryAccessCosts
View on GitHub ↗ ★ 13 C++
6 mentions on Hacker News by 2 people: 1 story, 5 comments · first 2018-08-02 · latest 2018-09-19
20082026
-
> Rust autovectorizes a lot better than C What C do you mean? Compilers aren't equal: https://github.com/Const-me/MemoryAccessCosts
comment by Const-me · 2018-09-19 · in Falling in love with Rust -
…reason is automatic vectorization. I’ve found the reason and wrote the readme after that comment: https://github.com/Const-me/MemoryAccessCosts/commits/master
comment by Const-me · 2018-08-02 · in Getting 4 bytes or a full cache line: same speed or not? -
…I found that? I’ve made a version portable across compilers, built with VC++ and run on Windows: https://github.com/Const-me/MemoryAccessCosts I don’t have Intel compiler but my expectation is it’ll work even better. Yes! You have found…
comment by ordu · 2018-08-02 · in Getting 4 bytes or a full cache line: same speed or not? -
…I found that? I’ve made a version portable across compilers, built with VC++ and run on Windows: https://github.com/Const-me/MemoryAccessCosts I don’t have Intel compiler but my expectation is it’ll work even better.
comment by Const-me · 2018-08-02 · in Getting 4 bytes or a full cache line: same speed or not? -
▲ 2
Getting 4 bytes or a full cache line: same speed or not?story by Const-me · 2018-08-02 · 0 comments
-
…8% between 1 and 16. Here’s my portable version, scalar-only, C++, and slightly more optimized: https://github.com/Const-me/MemoryAccessCosts The results are in result-gcc.txt and result-msvc.txt in that repo. They’re from the same PC, I’m…
comment by Const-me · 2018-08-02 · in Getting 4 bytes or a full cache line: same speed or not?