Nicholas Vinen <[email protected]> wrote: > I think -Os should inline functions if doing so reduces code size > - e.g. they are declared inline and only called in one place.
Inlining decisions are often based on heuristics, so their guesses about whether the inlining really safes code or not might occasionally be a little off. (In addition to saving the CALL/RET instructions, inlining a function can also cause other, not fully predictable saving due to the different register usage etc.) However, I think -fno-inline is always meant to prevent *all* functions from being inlined based on heuristics (except those that are qualified by attribute "always_inline"), so I'd consider this a bug here. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) _______________________________________________ AVR-GCC-list mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/avr-gcc-list
