Bug#325131: gcc-4.0: regression on hppa and arm, possibly wrong code
On Fri, Aug 26, 2005 at 01:27:43PM +0200, Falk Hueffner wrote:
> Max Vozeler <xam@debian.org> writes:
>
> > I can reproduce the problem in paer's sid chroot (hppa) and have put
> > gcc-3.4 and gcc-4.0 builds with -save-temps on [1]. If there is
> > other information that could be useful to you, please let me know.
>
> It would be nice to know how to reproduce the problem.
>
Note sure if this is what you are asking, if you copy the
2.3b-gcc-4.0 directory [1] to a hppa machine and run "make tests"
there it should show the wrong result.
I can tell that sha512.c is at fault because tests involving
AES128/192/256 using a different hash function (-H rmd160) gave
expected results.
Further reduced:
dd if=/dev/zero of=test-file3 bs=1024 count=10
echo 12345678901234567890 >test-file4
./aespipe -p 3 -e AES256 -H SHA512 -C 0 < test-file3 > test-file1 \
3<test-file4
md5sum test-file1
should show md5sum 818fa5f242bd2ff55244acbde0e9fd8f. This is
returned correctly by gcc-3.4 -O2 and gcc-4.0 -O1 builds.
Using gcc-4.0 -O2, the result is md5sum
8eecefa861d45341a8efeec0e2e578d2 instead.
cheers,
Max
[1] <http://people.debian.org/~xam/aespipe/hppa/>
Reply to: