> -----Original Message----- > From: > avr-gcc-list-bounces+eweddington=cso.atmel....@nongnu.org > [mailto:avr-gcc-list-bounces+eweddington=cso.atmel....@nongnu. > org] On Behalf Of larry barello > Sent: Monday, February 16, 2009 10:37 AM > To: avr-gcc-list@nongnu.org > Subject: [avr-gcc-list] GCC code gen on xmega > > Finally, I suppose if it was simple it would have been done > already:
You can't always make that assumption. ;-) > if > there are multiple calls to "printf" and friends, the entire > sequence of > setting up and tearing down the stack occurs over and over > again - and that > is on top of any setup and teardown performed for the function (say, a > buffer on the stack). > > In general, this kind of code inefficiency doesn't bother me > much because I > usually factor the routines to minimize the code, and the > processor is so > blazingly fast I don't care about the cycles. I just noticed > this while > looking for code sequences that might cause stack corruption. > Well, printf and friends are not very efficient anyway. Patches welcome. _______________________________________________ AVR-GCC-list mailing list AVR-GCC-list@nongnu.org http://lists.nongnu.org/mailman/listinfo/avr-gcc-list
