AVR-Chat

>   GCC might be a rude surprise then!  There is an init section of code
> linked in that handles startup housekeeping that will take up several
> hundred bytes.  That is what handles the "int foo = 1;" stuff, so I
> don't think that is avoidable.  Of course it also handles setting up the
> call stack, DATA heap and all the rest of the stuff that goes into a
> high level language.  If you are coming from assembly programming it all
> looks pretty "dirty", but essential.

Yea, some things are going to be unavoidable.  My main intention with
this is to learn C, specifically in GCC, but my ulterior motive if you
will, is to learn C for microcontrollers, so I picked up an AVR
package that had plenty of examples and tutorials specifically for
that hardware platform.

The company wants me more skilled with C so I can assist in low-level
debug as we bring up prototypes, (me being officially "the hardware
guy") but I also need to learn C for me, with an eye to using it on
small systems..

So, I'm trying not to loose sight of the small systems, but letting go
of what I must in order to get going in C.