> Then why are you writing C? You could be writing some other, higher-level language instead if performance is not your top priority. This goal seems somewhat

> Then why are you writing C? You could be writing some other, higher-level language instead if performance is not your top priority. This goal seems somewhat oxymoronic - if the "goal" is to be keenly aware of what the compiler will do and double check all assembly, then you shouldnt use C. If the goal is to ignore assembly and not pay attention to these sorts of things, then you shouldnt use C. The only valid niche I see is where the goal is to use C, not really have to worry about the assembly, have it do the "right" thing on your platform. I.e. no undefined behavior, just underperforming (and called out as such). Then you can go in and "approve" various optimizations.