[ANNOUNCEMENT] Updated: gcc-6.3.0-2 (x86/x86_64)(Test)

[Marco Atzeri]

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