🚀 go-pugleaf

I have a suggestion for the gcc project.

One of the big strengths of gcc is the fact that it runs on
everything, and a program is spared the weird hassles which sometimes
pop up when porting clean ANSI C from one ANSI compiler to another.

In some sense, it's hence useful for me to think i.t.o. "writing for
gcc -ansi -pedantic" rather than "writing for ANSI C".

This process would be much assisted by documentation about gcc
optimisation which is pitched at the programmer (i.e. not a compilers
guy).  I would really love to know everything there is to know about
gcc optimisation, this will help me know how to write code better.
I'm sure my code right now is making mistakes in working for
efficiency in situations when gcc will get it right anyway, and
counting on gcc to get things right at times when he won't.

These details will vary from one compiler to the next, of course, but
I don't forsee ever using a C compiler other than gcc, and I'm sure
many others are in the same situation.

Thanks,

        -ans.
-- 
Ajay Shah, (213)749-8133, ajayshah@rcf.usc.edu