This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug go/48122] crypto/aes test fails on 32-bit Solaris 11/x86


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48122

--- Comment #1 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> 2011-04-11 13:15:45 UTC ---
I noticed that this error only happens in a modifed tree with the libgo
multilib check patch

    http://gcc.gnu.org/ml/gcc-patches/2011-04/msg00247.html

Investigation showed that _testmain.go differs between the two trees:

--- ./_testmain.go      2011-04-09 20:39:58.824574614 +0200
+++
/var/gcc/gcc-4.7.0-20110408/11-gcc-gas/i386-pc-solaris2.11/libgo/crypto-aes-check/_testmain.go
     2011-04-09 20:38:06.328947345 +0200
@@ -14,8 +14,8 @@
        {"aes.TestExpandKey", aes.TestExpandKey},
        {"aes.TestEncryptBlock", aes.TestEncryptBlock},
        {"aes.TestDecryptBlock", aes.TestDecryptBlock},
-       {"aes.TestCipherEncrypt", aes.TestCipherEncrypt},
        {"aes.TestCipherDecrypt", aes.TestCipherDecrypt},
+       {"aes.TestCipherEncrypt", aes.TestCipherEncrypt},
 }
 var benchmarks = []testing.InternalBenchmark{ //
 }

It turns out that this was caused by passing $GOCFLAGS in CHECK (GC),
which was meant to pass the multilib flags, but isn't necessary since
those are included in $GOC.

But unfortunately the default (-g -O2) changes the outcome of this and a
couple of others tests.  I don't think the tests should be so fragile.

    Rainer


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]