what is your point?

If you don't follow the standard, gcc -O2 can introduce bugs to your code that you never even wrote. Skipping null checks, executing both branches of a conditional, and so on.

▲

jstimpfle an hour ago | parent [-]

Where did I say I'm not following the standard?

	▲	Xirdus 27 minutes ago \| parent [-]
		I interpreted these words: > If you want to be standards correct, yes you have to know the standard well. to mean that being standards-correct is optional. It's not. Every C programmer needs to know every possible UB by heart and never introduce any of it to their code, or else they'll be constantly introducing subtle, hard to debug bugs that contradict the actual code they wrote. Maybe you meant something different by those words, but then I'm confused what the "if" was supposed to mean.