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/65717] New: 64-bit runtime FAILs with 32-bit compiler Date: Thu, 09 Apr 2015 15:18:00 -0000 [thread overview] Message-ID: <bug-65717-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65717 Bug ID: 65717 Summary: 64-bit runtime FAILs with 32-bit compiler Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: go Assignee: ian at airs dot com Reporter: ro at gcc dot gnu.org CC: cmang at google dot com Host: i386-pc-solaris2.1[01], sparc-sun-solaris2.1[01], i686-unknown-linux-gnu Target: *-*-solaris2.1[01], i686-unknown-linux-gnu The 64-bit libgo runtime test FAILs on both Solaris and Linux when compiled with a 32-bit compiler: gc_test.go:187:19: error: invalid array length hugeSink = new([n]*byte) ^ gc_test.go:188:19: error: invalid array length hugeSink = new([n]uintptr) ^ gc_test.go:191:7: error: invalid array length y [n]*byte ^ gc_test.go:196:7: error: invalid array length y [n]uintptr ^ FAIL: runtime Everything is fine if using a 64-bit compiler instead. Rainer
next reply other threads:[~2015-04-09 15:18 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-04-09 15:18 ro at gcc dot gnu.org [this message] 2015-04-10 7:39 ` [Bug go/65717] " rguenth at gcc dot gnu.org 2015-04-10 8:09 ` ro at CeBiTec dot Uni-Bielefeld.DE 2015-04-22 12:02 ` jakub at gcc dot gnu.org 2015-07-16 9:15 ` rguenth at gcc dot gnu.org
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-65717-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).