I want to believe this is sarcasm, but it's so hard to tell these days.

For many cases like the one described, its true.

It's not. The majority of people regularly using GCC to develop C code (IOW, the primary use case of GCC) are familiar with assembly.

	▲	fragmede 18 minutes ago \| parent [-]
		How familiar? Do they ever look at the .S files? know what ar and nm do? Deal with objdump? How important are those details for day-to-day compiling of C code for regular programmers?

petcat 4 hours ago | parent | prev [-]

It's not sarcasm.

We've all accepted that code-generation has been required and accepted for decades.

Code generation (by compiler) has one major difference: it's deterministic.

Here are the reported miscompilation bugs in GCC so far in 2026. The ones labeled "wrong-code".

I count 500+ of them.

	▲	smallerize 2 hours ago \| parent \| next [-]
		That's not what "deterministic" means.
	▲	absoflutely 2 hours ago \| parent \| prev [-]
		Not sure what your point is here since wrong code doesn't mean non-deterministic. How many of these yield different results with the same input and architecture?