From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-456717-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 25756 invoked by alias); 18 Jul 2014 13:23:39 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Received: (qmail 25632 invoked by uid 48); 18 Jul 2014 13:23:36 -0000
From: "ian at airs dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/61840] [4.9 regression] sync/atomic FAILs on x86_64-unknown-linux-gnu
Date: Fri, 18 Jul 2014 13:23: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.9.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ian at airs 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: <bug-61840-4-QOv5MyLZUv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61840-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61840-4@http.gcc.gnu.org/bugzilla/>
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/msg01308.txt.bz2

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

--- Comment #2 from Ian Lance Taylor <ian at airs dot com> ---
Please tell us what kind of system you are running on and precisely how you ran
configure.

The error report doesn't make sense; it seems incomplete.  I don't see how the
test could fail without printing out more than that.  What happens if you cd
into the directory x86_64-unknown-linux-gnu/32/libgo and run "make
sync/atomic/check"?