fluffy87

11 ms·

91.
by fluffy87 7y ago
FWIW I applied to AMD for an HPC application engineer position (GPU compute) and a couple of weeks later to a similar position by a direct competitor. In the time it took the other company to contact me, do 6 interviews, negotiate contract,
92.
by fluffy87 7y ago
If you are writing applications that directly call OS ABIs you are doing it wrong. In the OpenBSD and Apple worlds, you can change an ABI because applications are expected to, as they should, call libc and similar platform abstraction libr
93.
by fluffy87 7y ago
I write standard compliant C++ code that only works with the latest compiler versions because older ones incorrectly claim support for C++ standard, but their implementation is too buggy.
94.
by fluffy87 7y ago
LLVM-IR is not properly specified, it changes significantly every 6 months (and even faster), and Rust exploits that
95.
by fluffy87 7y ago
Those tools suck.
96.
by fluffy87 7y ago
ATI was never in the AI market. They have been trying, but their efforts are a joke compared tobest their competition is doing.
97.
by fluffy87 7y ago
Not that it matters but you can use LTO with C++ and Rust, just need to compile and link both with LTO enabled.
98.
by fluffy87 7y ago
Yeah, there were differences, but these were peanuts. Using two different versions of GCC will givenyou similar differences.
99.
by fluffy87 7y ago
There has never been a PowerPC system that beats x86 at any price point.
100.
by fluffy87 7y ago
Do you have a link to the Tartine book? There are dozens of book by that name on amazon.
101.
by fluffy87 7y ago
Given the amount of subtle bugs that this has caused and continues to cause in Go, I don’t really consider this a benefit.
102.
by fluffy87 7y ago
> especially ones that try to do too much magic like TLS behind the scenes just to save me the trouble of supplying an instance/context pointer to every call. I really hate that this is the solution that Rust ended up pursuing. Ther