Re: Cleanup for cryptographic algorithms vs. compiler optimizations

Bernd Walter <ticso_at_cicely7.cicely.de> writes:
> Dag-Erling Smørgrav <des_at_des.no> 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.

DES
-- 
Dag-Erling Smørgrav - des_at_des.no