public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "boger at us dot ibm.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/63170] New: gccgo testcase recover.go fails execution with message 'missing recover' on ppc64 and ppc64le
Date: Thu, 04 Sep 2014 14:44:00 -0000 [thread overview]
Message-ID: <bug-63170-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63170
Bug ID: 63170
Summary: gccgo testcase recover.go fails execution with message
'missing recover' on ppc64 and ppc64le
Product: gcc
Version: 5.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: go
Assignee: ian at airs dot com
Reporter: boger at us dot ibm.com
CC: cmang at google dot com
gccgo was built from trunk on power8 machines for both ppc64 and ppc64le with
the same results
./gccgo --version
gccgo (GCC) 5.0.0 20140904 (experimental)
Copyright (C) 2014 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
This error occurs during make check testing for go for testcase:
gcc/testsuite/go.test/test/recover.go
Failing output for this testcase from go.log after running 'make check-gcc-go'
missing recover
Trace/breakpoint trap
main.die
/home/boger/gccgo.work/orig/trunk-src/gcc/testsuite/go.test/test/recover.go:69
main.mustRecoverBody
/home/boger/gccgo.work/orig/trunk-src/gcc/testsuite/go.test/test/recover.go:81
main.M.N7_main.T5
/home/boger/gccgo.work/orig/trunk-src/gcc/testsuite/go.test/test/recover.go:437
reflect.call
/home/boger/gccgo.work/orig/trunk-src/libgo/runtime/go-reflect-call.c:226
reflect.call.N13_reflect.Value
/home/boger/gccgo.work/orig/trunk-src/libgo/go/reflect/value.go:576
reflect.Call.N13_reflect.Value
/home/boger/gccgo.work/orig/trunk-src/libgo/go/reflect/value.go:412
reflect.$nested2
/home/boger/gccgo.work/orig/trunk-src/libgo/go/reflect/makefunc.go:175
reflect.ffiCall
/home/boger/gccgo.work/orig/trunk-src/libgo/go/reflect/makefunc_ffi.go:64
reflect.$nested3
/home/boger/gccgo.work/orig/trunk-src/libgo/go/reflect/makefunc_ffi.go:36
main.test13reflect2
/home/boger/gccgo.work/orig/trunk-src/gcc/testsuite/go.test/test/recover.go:456
main.main
/home/boger/gccgo.work/orig/trunk-src/gcc/testsuite/go.test/test/recover.go:58
goroutine 18 [finalizer wait]:
created by runtime_createfing
/home/boger/gccgo.work/orig/trunk-src/libgo/runtime/mgc0.c:2572
FAIL: go.test/test/recover.go execution, -O2 -g
next reply other threads:[~2014-09-04 14:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 14:44 boger at us dot ibm.com [this message]
2014-09-04 15:52 ` [Bug go/63170] " ian at airs dot com
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-63170-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).