From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-353185-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 25631 invoked by alias); 11 Apr 2011 13:15:57 -0000
Received: (qmail 25621 invoked by uid 22791); 11 Apr 2011 13:15:56 -0000
X-SWARE-Spam-Status: No, hits=-2.8 required=5.0	tests=ALL_TRUSTED,AWL,BAYES_00
X-Spam-Check-By: sourceware.org
Received: from localhost (HELO gcc.gnu.org) (127.0.0.1)    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 11 Apr 2011 13:15:51 +0000
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/48122] crypto/aes test fails on 32-bit Solaris 11/x86
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ro at CeBiTec dot Uni-Bielefeld.DE
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields:
Message-ID: <bug-48122-4-LFODg6IL3p@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-48122-4@http.gcc.gnu.org/bugzilla/>
References: <bug-48122-4@http.gcc.gnu.org/bugzilla/>
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
Date: Mon, 11 Apr 2011 13:15:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
X-SW-Source: 2011-04/txt/msg01089.txt.bz2

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