arthur2e5
Joined 10 years ago
Joined 10 years ago
Not that strongly for more parallel things, quite similar to the situation with atomics on cuDNN. cuBLAS for example has a similar issue with multi-stream handling, though this can be overcome with a proper workspace allocation: https://docs.nvidia.com/cuda/cublas/index.html?highlight=Rep....
Still better than cuDNN where some operations just don't have a reproducible version though. The other fields are at least trying. DL doesn't seem to be.
On that note Intel added reproducible BLAS to oneMKL on CPU and GPU last year. https://www.intel.com/content/www/us/en/developer/archive/tr...
https://godbolt.org/z/oof145zjb
So no, Haswell is not the problem. LLVM just doesn't know about the dependency thing.
Still, it's all LLVM, so perhaps unsafe Rust for Fil-space can be a thing, a useful one for catching (what would be) UBs even [Fil-C defines everything, so no UBs, but I'm assuming you want to eventually run it outside of Fil-space].
Now I actually wonder if Fil-C has an escape hatch somewhere for syscalls that it does not understand etc. Well it doesn't do inline assembly, so I shouldn't expect much... I wonder how far one needs to extend the asm clobber syntax for it to remotely come close to working.
Tangential: China technically banned metamizole due to the agranulocytosis scare, but somehow small clinics always have fresh stocks of this stuff. And their stocks don't look like my metamizole for horses! It's pressed out of the usual magnesium stearate instead of whatever rock-hard thing they use for animal drugs in China.
[]: https://github.com/boostorg/container_hash/commit/40ec854466...
There's also the nebulous but very nice-sounding "non-specific effect" with it. Who knows.
https://www.hamilton.edu/academics/centers/writing/seven-sin...