Re: aespipe testsuite failure - help
On Tue, Aug 23, 2005 at 02:35:09PM +0200, Max Vozeler wrote:
> aespipe includes a C implementation of SHA256/384/512 that is tested
> after the build. SHA384 and SHA512 currently generate wrong results on
> arm and hppa, whereas SHA256 works as expected on all archs.
> I can reproduce the failure in paer's sid chroot, but only with the
> combination of gcc-4.0 and -O2 optimisation. The gcc-3.4 and gcc-4.0
> builds including preprocessed sha512.c and generated .s are up on
> What I found out so far:
> - No problem with -O0 or -O1
> - No runtime problem, old binary passes the testsuite
> - No problem with gcc-3.3 or gcc-3.4
> - No difference in preprocessed sha512.c between gcc-3.4 and gcc-4.0
> Any suggestions how to proceed to debug/resolve this?
It certainly sounds like a gcc bug. So you can follow the instructions
at http://gcc.gnu.org/bugs.html to report it.
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain