From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12781 invoked by alias); 8 Jul 2014 21:39:28 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 12684 invoked by uid 48); 8 Jul 2014 21:39:20 -0000 From: "dvyukov at google dot com" 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: go X-Bugzilla-Version: 4.10.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dvyukov at google dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: ian at airs dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-07/txt/msg00508.txt.bz2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61308 --- Comment #2 from Dmitry Vyukov --- 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.