Cleanup for cryptographic algorithms vs. compiler optimizations

Dag-Erling Smørgrav des at
Sun Jun 13 21:43:15 UTC 2010

Bernd Walter <ticso at> writes:
> Dag-Erling Smørgrav <des at> writes:
> > The only way you can tell that gcc did it is if you break the rules,
> > such as by defining your own version of printf() or puts().
> Our loader stages do this for good reasons.  And in microcontroller
> programming (surely out of FreeBSD scope) it is done very regulary.

Those are freestanding environments, where printf() and puts() don't
exist as far as the C standard is concerned.

Dag-Erling Smørgrav - des at

More information about the freebsd-current mailing list