public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug go/48122] New: crypto/aes test fails on 32-bit Solaris 11/x86 Date: Mon, 14 Mar 2011 19:58:00 -0000 [thread overview] Message-ID: <bug-48122-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48122 Summary: crypto/aes test fails on 32-bit Solaris 11/x86 Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: go AssignedTo: ian@airs.com ReportedBy: ro@gcc.gnu.org Host: i386-pc-solaris2.11 Target: i386-pc-solaris2.11 Build: i386-pc-solaris2.11 The crypto/aes test recently started failing on 32-bit Solaris 11/x86 (only, 64-bit is fine): FAIL: crypto/aes --- FAIL: aes.TestCipherDecrypt decryptBlock 0: plain[0] = 0x0, want 0x32 decryptBlock 1: plain[1] = 0x0, want 0x11 decryptBlock 2: plain[1] = 0x0, want 0x11 decryptBlock 3: plain[1] = 0x0, want 0x11 --- FAIL: aes.TestCipherEncrypt Cipher.Encrypt 0: out[0] = 0x0, want 0x32 Cipher.Encrypt 1: out[1] = 0x0, want 0x11 Cipher.Encrypt 2: out[1] = 0x0, want 0x11 Cipher.Encrypt 3: out[1] = 0x0, want 0x11 FAIL make: *** [crypto/aes/check] Error 1 I'm pretty sure it worked before, but cannot be certain since libgo testsuite results don't show up in mail-report.log.
next reply other threads:[~2011-03-14 19:58 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-03-14 19:58 ro at gcc dot gnu.org [this message] 2011-04-11 13:15 ` [Bug go/48122] " ro at CeBiTec dot Uni-Bielefeld.DE 2012-02-14 19:47 ` ian at airs dot com 2012-02-16 19:45 ` ro at CeBiTec dot Uni-Bielefeld.DE
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-48122-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).