public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ian at airs dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/60874] FAIL: go.test/test/recover.go execution
Date: Tue, 05 Aug 2014 14:09:00 -0000	[thread overview]
Message-ID: <bug-60874-4-2sL22Ln9ZQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60874-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60874

--- Comment #6 from Ian Lance Taylor <ian at airs dot com> ---
I don't know why making the types smaller in comment #4 makes any difference. 
On a system that does not use split stacks, the runtime will allocate a 2M
stack for each goroutine (see StackMin in libgo/runtime/proc.c).  That is
clearly more than large enough to hold a 8192 byte value.  The comments in the
test about splitting the stack only apply to systems that support stack
splitting.

This will need more investigation by somebody with access to an Alpha.  I guess
one simple first step would be to verify that USING_SPLIT_STACK and
LINKER_SUPPORTS_SPLIT_STACK are both 0 in the file TARGET/libgo/config.h.


  parent reply	other threads:[~2014-08-05 14:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-17 18:14 [Bug go/60874] New: " ubizjak at gmail dot com
2014-07-20  8:27 ` [Bug go/60874] " ubizjak at gmail dot com
2014-07-20  9:12 ` ian at airs dot com
2014-07-21 12:31 ` ubizjak at gmail dot com
2014-07-21 14:35 ` ubizjak at gmail dot com
2014-08-05 14:09 ` ian at airs dot com [this message]
2014-08-05 14:14 ` ubizjak at gmail dot com
2014-08-06 13:00 ` ubizjak at gmail dot com
2014-08-06 13:03 ` ubizjak at gmail dot com
2014-08-06 13:12 ` schwab@linux-m68k.org
2014-08-06 13:27 ` ubizjak at gmail dot com
2014-08-06 13:56 ` ian at airs dot com
2014-08-06 14:17 ` ubizjak at gmail dot com
2014-08-06 17:16 ` ubizjak at gmail 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-60874-4-2sL22Ln9ZQ@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).