I was a bit surprised by how big some arduino programs were, so I did a few tests. With nothing in the setup and loop procedures, the compiled file is 450 bytes, which is more than the wource code. I've noticed problems with size a lot, and I've been wondering how the compiler works. Does it always include the entire main library, or is it optimized to only include functions that are used? If it doesn't optimize code, I guess this thread goes in the suggestion forum. Anyway, my wuestion is whether the compiled progams are optimized. Thanks!
With nothing in the setup and loop procedures, the compiled file is 450 bytes, which is more than the wource code.
Which includes the startup code for the C run time library and the interrupt vector table.
Does it always include the entire main library
No.
or is it optimized to only include functions that are used?
Yes.
Anyway, my wuestion is whether the compiled progams are optimized.
Highly optimized.
Thanks!
You are welcome.
Ok. That all makes good sense then. Of course, the counters that were used for compatibility should be optional at compile time. (In my humble opinion) Of course, I'm not an arduino genius, so what it's like right now is much better than anything I can think of. ;D