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/51874] New: Many libgo testsuite failures on Solaris, IRIX
Date: Mon, 16 Jan 2012 18:11:00 -0000 [thread overview]
Message-ID: <bug-51874-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51874
Bug #: 51874
Summary: Many libgo testsuite failures on Solaris, IRIX
Classification: Unclassified
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Severity: major
Priority: P3
Component: go
AssignedTo: ian@airs.com
ReportedBy: ro@gcc.gnu.org
Host: i386-pc-solaris2.1[01], mips-sgi-irix6.5
Target: i386-pc-solaris2.1[01], mips-sgi-irix6.5
Build: i386-pc-solaris2.1[01], mips-sgi-irix6.5
Since the introduction of
runtime: Multiplex goroutines onto OS threads.
go and libgo testsuite results on Solaris and IRIX have become terrible to the
point that Go is unusable on both platforms:
* On Solaris 10 and 11/x86, all 64-bit libgo tests FAIL now, while the 32-bit
tests are fine. 64-bit go.test results show several failures too:
FAIL: ./select5-out.go compilation, -O2 -g
FAIL: go.test/test/chan/doubleselect.go execution, -O2 -g
FAIL: go.test/test/chan/nonblock.go execution, -O2 -g
FAIL: go.test/test/chan/select2.go execution, -O2 -g
FAIL: go.test/test/chan/select3.go execution, -O2 -g
FAIL: go.test/test/mallocfin.go execution, -O2 -g
FAIL: go.test/test/stack.go execution, -O2 -g
WARNING: program timed out.
WARNING: program timed out.
* The situation on Solaris/SPARC is similar: about half of both 32-bit and
64-bit
libgo tests FAIL. The set of failing go.tests is also much larger than on
x86.
* On IRIX 6.5, all libgo tets FAIL, both 32 and 64-bit. The set of failing
go.test tests seems similar to the Solaris/SPARC case.
Initially, I've tried to investigate an existing 64-bit Solaris/x86 testcase
(mallocfin), but that proved to be difficult.
I've now found a far simpler one: an empty main.go fails if run with
GOMAXPROCS=2:
panic: runtime error: invalid memory address or nil pointer dereference
I find that g->entry is NULL at the first kickstart call, while it has been
initialized to mainstart before. I've not yet found how this happens.
Rainer
next reply other threads:[~2012-01-16 17:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-16 18:11 ro at gcc dot gnu.org [this message]
2012-01-27 12:18 ` [Bug go/51874] " ro at gcc dot gnu.org
2012-01-27 12:35 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-01-27 13:04 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-01-31 19:01 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-02-11 0:07 ` ian at airs dot com
2012-02-12 6:01 ` ian at gcc dot gnu.org
2012-02-12 6:05 ` ian at airs dot com
2012-02-12 6:06 ` ian at airs dot com
2012-02-12 6:55 ` pinskia at gcc dot gnu.org
2012-02-14 18:20 ` ian at airs dot com
2012-02-14 18:32 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-02-16 7:31 ` ian at gcc dot gnu.org
2012-02-16 19:46 ` [Bug go/51874] Many libgo testsuite failures on IRIX ro at gcc dot gnu.org
2012-03-22 8:57 ` rguenth at gcc dot gnu.org
2012-04-04 11:49 ` ro at gcc dot gnu.org
2012-04-24 16:33 ` ian at airs dot com
2012-05-08 15:10 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-05-08 15:20 ` ro at gcc dot gnu.org
2012-07-02 14:10 ` rguenth at gcc dot gnu.org
2014-06-13 11:41 ` ro 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-51874-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: link
Be 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).