Cleanup for cryptographic algorithms vs. compiler optimizations

[Andrew Milton]

+-------[ Bernd Walter ]----------------------
| On Sun, Jun 13, 2010 at 05:44:29PM +0200, Dag-Erling Smørgrav wrote:
| > Bernd Walter <ticso at cicely7.cicely.de> writes:
| > > Amazing - this is one of the things which can get nasty if you try some
| > > kind of microtuning.
| > 
| > Only if you break the rules.  Bad code is always bad, even if it
| > sometimes works by accident.
| 
| To expect that function calls are replaced with other functions isn't a
| very obvious rule.

Don't turn on compiler optimisation then. You're explicitly telling
the compiler to make your code better/faster/smaller. Optimisation
flags always come with the caveat that your code may not work exactly 
the same...

-- 
Andrew Milton
akm at theinternet.com.au