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/67968] go1: internal compiler error: in write_specific_type_functions, at go/gofrontend/types.cc:1812
Date: Fri, 23 Oct 2015 16:59:00 -0000	[thread overview]
Message-ID: <bug-67968-4-bqTs1uCpXH@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 #7 from Ian Lance Taylor <ian at airs dot com> ---
Dominik: Chris has committed a number of recent fixes for gccgo compiler
crashes.  Are you testing with current mainline or with the 5.2.1 release that
gong_su is using?  Or is the problem that you don't have the imported packages?

If that is the problem, then I wouldn't worry about shrinking the number or
size of the input files.  The only thing that matters is reducing the number of
imports.

Or, it's likely to be easier to just tar up the import files.  Once this kind
of problem can be reproduced, it's usually easy to fix.


  parent reply	other threads:[~2015-10-23 16:59 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
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 [this message]
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-bqTs1uCpXH@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).