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=Gh4dKz+boA8C/v01
	6BlOtf6LFkiByzQwEJAUYiFw9cPnIc9sfs1J+BZQAe27TPoPOeX7btibw81t5sp9
	w7ZafAkrsdO3gi/3Gc0ta0V9I28pj+QNXcNo9dtM0WJBWicxOlijtfMXzx/p+G8t
	u50XPBJ1EjTBiNlHPS0SQwfyoLU=
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=iOgb/lKPgVWJv6T8fr0HOv
	mwwFc=; b=sk4h5nfVPls4o9i/wYCXQdYaFkWK8zOJQ37W9eov3JuejOMyqh1ymW
	Ec/+gznmNw2dv307oi75P06zJgsfVI1koyCWzkk4wmwCLsOSmKOeaYcnjKgqZjeX
	Vp/QZjtGQ0/JRWurwCIwrpviuv0IJ8vlIKNvAr0GHy79zOB8FP/lA=
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.4 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=no version=3.3.2 spammy=
X-HELO: mail-wr0-f193.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:references:from:message-id:date         :user-agent:mime-version:in-reply-to:content-transfer-encoding;        bh=135bYiLruh7BIvLN7piAW0XBrqYSkOHEhPs8hSCR1bk=;        b=st+1mcyuK7i/Xo1j5f9zub14UvZCPTRKFSZAsv5+HQ9hbqYTMpu/Y6Yn2cVwgCbRuy         E+FN0isOTeWmhu3VX6yfDx6ztvfKIycGdOq1xXRZtKNTCulLDS2RBOSleN1YAAiO4CL/         3s5RF2VywpGJRaCGFpWFJ0cSur6vKWXQ7MNa7qpBYx7vNCdRRPkKaU7QckI0GMpOnM7g         dUDUc51KmJrUT+p4wPvie4HoYCgMk33YuwHZEzphoxv50y2im7aoNwZR+Vrk4En32gOu         CVH0dcjFasJ1jwcJuVD7GXvkyWcpm6YMHLnG8CNlygZ4wUsmPO0gALHArRB9yVGqccuQ         U8nA==
X-Gm-Message-State: AIVw111wvmsE1gzUifCFsaaXoFjwZ4qVKIRXxjrlEdrCXHHWRdykHznv	jepGEz33zVXm+P1V
X-Received: by 10.223.178.212 with SMTP id g78mr4465972wrd.144.1501190349153;        Thu, 27 Jul 2017 14:19:09 -0700 (PDT)
Subject: Re: [ANNOUNCEMENT] Updated: gcc-6.3.0-2 (x86/x86_64)(Test)
To: cygwin@cygwin.com
References: <announce.db6c6795-264e-0936-152e-cfc7adbe2799@gmail.com> <8dd126b8-69aa-fb61-c12a-3d4afb821a66@cornell.edu> <1a57c104-79d1-2ea7-90d3-2be3182a2e1e@otoy.com>
From: Marco Atzeri <marco.atzeri@gmail.com>
Message-ID: <120c0997-0182-f4e6-0dfd-5d5afd6fd182@gmail.com>
Date: Thu, 27 Jul 2017 23:19:01 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <1a57c104-79d1-2ea7-90d3-2be3182a2e1e@otoy.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

On 27/07/2017 23:04, Ross Smith wrote:
> 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
>

it works for me on W7-64

./thread || echo "fail"
Start
Thread
Done

$ g++ --version
g++ (GCC) 6.3.0


--
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