public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug go/51874] New: Many libgo testsuite failures on Solaris, IRIX
@ 2012-01-16 18:11 ro at gcc dot gnu.org
  2012-01-27 12:18 ` [Bug go/51874] " ro at gcc dot gnu.org
                   ` (19 more replies)
  0 siblings, 20 replies; 21+ messages in thread
From: ro at gcc dot gnu.org @ 2012-01-16 18:11 UTC (permalink / raw)
  To: gcc-bugs

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


^ permalink raw reply	[flat|nested] 21+ messages in thread
end of thread, other threads:[~2014-06-13 11:41 UTC | newest]

Thread overview: 21+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-01-16 18:11 [Bug go/51874] New: Many libgo testsuite failures on Solaris, IRIX ro at gcc dot gnu.org
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

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).