public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dvyukov at google dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/61308] gccgo: ICE in Expression::check_bounds [GoSmith]
Date: Tue, 08 Jul 2014 21:39:00 -0000	[thread overview]
Message-ID: <bug-61308-4-5hUFAGGdoi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61308-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Dmitry Vyukov <dvyukov at google dot com> ---
It would be great to accompany these fixes with regression tests. We have
significant amount of Go code in std lib and tests, but still we discover new
code patterns. Any new compiler functionality (like race detector or coverage
analysis) would benefit from extensive tests.
Does gccgo use tests from the main Go repo? The main repo looks like the best
place for them.


  parent reply	other threads:[~2014-07-08 21:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-25  7:21 [Bug go/61308] New: " dvyukov at google dot com
2014-07-08 21:29 ` [Bug go/61308] " ian at gcc dot gnu.org
2014-07-08 21:39 ` dvyukov at google dot com [this message]
2014-08-05  2:51 ` ian at airs dot com
2014-08-05  2:58 ` ian at gcc dot gnu.org
2014-08-05  3:11 ` ian at gcc dot gnu.org
2014-08-05  3:11 ` ian at gcc dot gnu.org
2014-08-05  3:21 ` 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-61308-4-5hUFAGGdoi@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).