fluffy87

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, and get me signed, I haven’t even been contacted by AMD. Their position is still open, I’m a perfect fit and I haven’t been rejected either. I suppose I’ll get an automatic rejection letter at some point.

The online application system for AMD is just quite bad. Looking at my application in their system, everything is full with “Unknown” and I can’t event put in my skills. It wouldn’t surprise me if on their database I’m a horrible candidate.

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 libraries instead, and these libraries are dynamically linked.

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.

LLVM-IR is not properly specified, it changes significantly every 6 months (and even faster), and Rust exploits that

Those tools suck.

ATI was never in the AI market. They have been trying, but their efforts are a joke compared tobest their competition is doing.

Not that it matters but you can use LTO with C++ and Rust, just need to compile and link both with LTO enabled.

Yeah, there were differences, but these were peanuts. Using two different versions of GCC will givenyou similar differences.

There has never been a PowerPC system that beats x86 at any price point.

Do you have a link to the Tartine book? There are dozens of book by that name on amazon.

Given the amount of subtle bugs that this has caused and continues to cause in Go, I don’t really consider this a benefit.

> 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. There are claims that you can work around TLS by just no using TLS if it is not available, but I have yet to see someone removing TLS and still be able to use a multi-threaded executor.