Follow-up Comment #4, bug #50811 (project avr-libc):
You're correct, there's no reason when printf isn't being used to use those
linker options. However:
* realistically at least some linker options are at least somewhat black magic
to many users.
* printf() is particularly likely to go from unused to used during debugging,
during which large swings in code size may be extra confusing
For these reasons, I still think adding something to the documentation would
make sense. It could be as simple as one sentence explaining what you just
explained:
"Note that if your program doesn't end up calling vfprintf(), using the
printf_min linker flags will increase code size because it forces the
vfprintf() function to be included even though it isn't used."
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?50811>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/
_______________________________________________
AVR-libc-dev mailing list
AVR-libc-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/avr-libc-dev
