public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vogt at linux dot vnet.ibm.com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug go/67968] go1: internal compiler error: in write_specific_type_functions, at go/gofrontend/types.cc:1812 Date: Thu, 22 Oct 2015 09:45:00 -0000 [thread overview] Message-ID: <bug-67968-4-tkRu0esGkt@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-67968-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67968 --- Comment #3 from Dominik Vogt <vogt at linux dot vnet.ibm.com> --- To narrow down where the problem happens please try this: 1. Edit the first line of the file build/env.sh and append "-a": #!/bin/sh -a 2. Locate the gccgo executable (whould be in the path GOBIN that is set in the Makefile) and rename it: $ mv gccgo gccgo.bin 3. Place this small script with the name "gccgo" into the directory with gccgo.bin and make it executable: #!/bin/sh exec "$GOBIN"/gccgo.bin -v $@ $ chmod 755 gccgo Finally the GOBIN directory should look like this: $ ls -l gccgo* -rwxr-xr-x 1 ... 40 ... gccgo -rwxr-xr-x 2 ... 13M ... gccgo.bin 4. Built ethereum als usual. Gccgo now prints all commands it executes, and hopefully the failing command last. Please attach this output to the bug report. Also, please make a tar archive of only the source files listed in the failing "go1" command line, compress it with "bzip2 -9" or 7zip and send it to me via email.
next prev parent reply other threads:[~2015-10-22 9:45 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-10-14 17:25 [Bug go/67968] New: " gong_su at hotmail dot com 2015-10-15 14:06 ` [Bug go/67968] " vogt at linux dot vnet.ibm.com 2015-10-22 9:45 ` vogt at linux dot vnet.ibm.com [this message] 2015-10-23 12:38 ` vogt at linux dot vnet.ibm.com 2015-10-23 12:39 ` vogt at linux dot vnet.ibm.com 2015-10-23 16:59 ` ian at airs dot com 2015-10-23 17:08 ` vogt at linux dot vnet.ibm.com 2015-10-23 17:42 ` ian at airs dot com 2015-10-26 12:03 ` vogt at linux dot vnet.ibm.com 2015-10-27 10:21 ` vogt at linux dot vnet.ibm.com 2015-10-28 15:44 ` gong_su at hotmail 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-67968-4-tkRu0esGkt@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).