X-Recipient: archive-cygwin@delorie.com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=rvJYzfPGbJyz14lU
	IV5y1TtW+mtytzDKpscpo4tSgv6PQThuWjjKBcaxnRxrwe/Szsq+eohrH8TSSiag
	fh87GkJdZbDbFHFE4Rdy5axT7k360/4c3l0LgO8o1S3dimnsZvWYTpRiaVbu+7z7
	+Af5XbJk/hE0/oMOwTlD7wTwJVY=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=tTUH/81NqnGaDANHpRsLdB
	bd/hc=; b=ArixEERoN3iR22BTAWs7kMxy4MuCax6xY7mR0azXx4x0yIl/mSEubd
	78NnMgjU5Pcp+gvs39heoasjvC6F+NzMAoBdNb33qEfb73SAgssG4Pc1FyPADmL0
	HqeJ+JnZUpPpHN8JkyDWKo5/ss1MDk+KVTCnMOGRNZX0Mpoh4XXR4=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=
X-HELO: mail-pg0-f53.google.com
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=1e100.net; s=20161025;        h=x-gm-message-state:subject:to:newsgroups:references:from:message-id         :date:user-agent:mime-version:in-reply-to:content-language         :content-transfer-encoding;        bh=cOrfryS6hoM62X+bIahWnUxlIQVKW+gTD2ENqiqTSOc=;        b=NjcgnFO43rpI8TVtvVWGBgHsq6RwQ/z6+bdclWM+RlAJFC9WkqrwDwPbsTnC/Weogu         hYSMvZd3952/1ln3FpYRiC4h98IWQif1/zck60egC0AwshBuKbavjqlqqcRzoaVqDQZH         IDdyZ4P93rKljl1uOFNXpVy7nYCHhRLwjA2WxYgQv0eiJmyo0f2bn3sv8xQYe8IyYVRi         HY08w5wCM0z5rDnqm73bNC1vuvBz83SWcJm3J+MdySvgwu4d/7KzkJi0KtDEEvNJmSoi         fOCHd3wXYT6FMGO+M9lera18B3Ngs6yh+0KMjlwp3+Zy9Pg6aRW2CQkXaidKLKzPrtZ3         uh3g==
X-Gm-Message-State: AIVw111GY03c55nHsYx5RjQtQ9gvbUwLqk80ppU7WC6jw4jhW3mkjZ+I	QkHI4wTtGNATq4AzY9o=
X-Received: by 10.98.1.20 with SMTP id 20mr5218476pfb.246.1501189495845;        Thu, 27 Jul 2017 14:04:55 -0700 (PDT)
Subject: Re: [ANNOUNCEMENT] Updated: gcc-6.3.0-2 (x86/x86_64)(Test)
To: cygwin@cygwin.com
Newsgroups: gmane.os.cygwin
References: <announce.db6c6795-264e-0936-152e-cfc7adbe2799@gmail.com> <8dd126b8-69aa-fb61-c12a-3d4afb821a66@cornell.edu>
From: Ross Smith <ross.smith@otoy.com>
Message-ID: <1a57c104-79d1-2ea7-90d3-2be3182a2e1e@otoy.com>
Date: Fri, 28 Jul 2017 09:04:52 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <8dd126b8-69aa-fb61-c12a-3d4afb821a66@cornell.edu>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

On 2017-07-28 02:49, Ken Brown wrote:
> On 6/29/2017 7:16 AM, JonY wrote:
>> gcc-6.3.0-2 has been uploaded for Cygwin. It is marked as a test version.
> 
> JonY,
> 
> I assume you want some feedback on this.
> 
> I've been testing gcc-6.3.0-2 with binutils-2.28-3, on both x86 and 
> x86_64, by rebuilding several of my packages.  So far I've built 
> texlive, emacs, and icu.  There have been no problems, and all builds 
> have passed their test suites.
> 
> Ken

gcc 6.3 works fine for me unless I use threads. Any C++ program that 
uses std::thread (and worked with the previous gcc) will fail. Simple 
example:

     #include <iostream>
     #include <thread>
     void payload() {
         std::cout << "Thread\n";
     }
     int main() {
         std::cout << "Start\n";
         std::thread t(payload);
         t.join();
         std::cout << "Done\n";
     }

Build and run with:

     g++ thread.cpp -o thread && ./thread || echo Fail

This will print Fail, indicating that the executable errored out. 
There's no other output. Sorry, I'm not familiar enough with gcc 
debugging to narrow down the error further.

Code that uses raw pthreads instead of the C++ API works fine.

(I'm running 64-bit Cygwin on Windows 8.1.)

Ross Smith

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple