> When was the last time you reviewed the machine code produced by a compiler? ...
I use Godbolt regularly, as do many C and C++ devs, for the sake of optimization, but I'm not sure that's what you mean. Checking the generated output is sometimes still needed for correctness, probably more so in the past than now due to threads not being a part of the language and the memory model being under-specified (allowing compiler authors to assume a single-threaded execution model), but those were deficiencies in those languages in particular (since remedied). Paradoxically, it's also still sometimes needed to ensure the compiler doesn't optimize certain code away, for the sake of security.
I use Godbolt regularly, as do many C and C++ devs, for the sake of optimization, but I'm not sure that's what you mean. Checking the generated output is sometimes still needed for correctness, probably more so in the past than now due to threads not being a part of the language and the memory model being under-specified (allowing compiler authors to assume a single-threaded execution model), but those were deficiencies in those languages in particular (since remedied). Paradoxically, it's also still sometimes needed to ensure the compiler doesn't optimize certain code away, for the sake of security.