Cleanup for cryptographic algorithms vs. compiler optimizations
ticso at cicely7.cicely.de
Sun Jun 13 22:05:51 UTC 2010
On Sun, Jun 13, 2010 at 11:41:03PM +0200, Dag-Erling Smørgrav wrote:
> 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.
Most controller environments have some kind of libc.
We even have devel/avr-libc and devel/msp430-libc in ports.
Anyway - printf=>puts isn't scarying as such, it is more that this might
happen in other cases as well.
B.Walter <bernd at bwct.de> http://www.bwct.de
Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.
More information about the freebsd-current