What's wrong with GOTO?

Saying that GOTO is wrong is like saying that pointers are wrong.

If you didn't know, your CPU doesn't call functions. It "calls" addresses or jumps, like, GOTO 10, which may be written in x86 assembly as JMP 10. You may have noticed that it's a direct translation, so using goto in languages like C gives the programmer even more flexibility for optimizations - more than using lots of functions and macro crap.

>>11
I've always read that gcc's optimizer (specifically, it's C optimizer) is subpar compared to, say, Intel's or ARM's optimizers. The benefit to using gcc has always been explained to me as "it'll build on anything", that gcc while somewhat less efficient than single-architecture compilers in that it has the widest selection of target platforms.