public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "anton at samba dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug go/60931] New: libgo has issues when page size is not 4k Date: Wed, 23 Apr 2014 07:06:00 -0000 [thread overview] Message-ID: <bug-60931-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60931 Bug ID: 60931 Summary: libgo has issues when page size is not 4k Product: gcc Version: 4.10.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: go Assignee: ian at airs dot com Reporter: anton at samba dot org Created attachment 32659 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=32659&action=edit Bump page size to 64kB We are seeing random failures with go programs on a 64kB page size ppc64 box. It looks like garbage collection issues - sometimes we SEGV in timer code, sometimes we SEGV in the code that wraps a kernel read syscall. If I prevent the garbage collector from running, the programs work. The libgo malloc hard codes the page size so I wrote a quick hack to bump this (and a few other dependent variables). This makes the problem go away, but we will need to come up with a better way to do this at runtime.
next reply other threads:[~2014-04-23 7:06 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-04-23 7:06 anton at samba dot org [this message] 2014-04-23 7:11 ` [Bug go/60931] " pinskia at gcc dot gnu.org 2014-04-23 7:27 ` anton at samba dot org 2014-04-23 16:42 ` ian at airs dot com 2014-04-24 0:17 ` anton at samba dot org 2014-04-24 0:18 ` anton at samba dot org 2014-04-24 5:38 ` jakub at gcc dot gnu.org 2014-04-25 4:29 ` ian at gcc dot gnu.org 2014-04-25 4:29 ` ian at gcc dot gnu.org 2014-04-25 4:33 ` 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-60931-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).