Re: [Mingw-w64-public] gcc 5.2.1 libgomp testsuite failures with latest runtime and winpthread

2015-09-11 9:53 GMT+02:00 Rainer Emrich : > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Ping! > > Am 29.08.2015 um 23:00 schrieb Kai Tietz: >> >> Am 09.08.2015 19:17 schrieb "Mattias Engdegård" > >: >>> >>> 7 aug

Re: [Mingw-w64-public] gcc 5.2.1 libgomp testsuite failures with latest runtime and winpthread

On Fri, Sep 11, 2015, Michel Zou wrote: > > You can ping the gcc dudes instead ! > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67141 Considering the issue, I doubt that only libgomp has the sloppy coding. :) -- Adrien Nader

Re: [Mingw-w64-public] gcc 5.2.1 libgomp testsuite failures with latest runtime and winpthread

You can ping the gcc dudes instead ! https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67141 > Date: Fri, 11 Sep 2015 09:54:16 +0200 > From: sf.rai...@emrich-ebersheim.de > To: mingw-w64-public@lists.sourceforge.net > Subject: Re: [Mingw-w64-public] gcc 5.2.1 libgomp testsuite failures wi

Re: [Mingw-w64-public] gcc 5.2.1 libgomp testsuite failures with latest runtime and winpthread

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Ping! Am 29.08.2015 um 23:00 schrieb Kai Tietz: > > Am 09.08.2015 19:17 schrieb "Mattias Engdegård" >: >> >> 7 aug 2015 kl. 14.50 skrev Rainer Emrich

Re: [Mingw-w64-public] gcc 5.2.1 libgomp testsuite failures with latest runtime and winpthread

Ping! Am 29.08.2015 um 23:00 schrieb Kai Tietz: > > Am 09.08.2015 19:17 schrieb "Mattias Engdegård" >: >> >> 7 aug 2015 kl. 14.50 skrev Rainer Emrich >: >> >> > This fixes the issue,

Re: [Mingw-w64-public] gcc 5.2.1 libgomp testsuite failures with latest runtime and winpthread

Hi, I committed code to tolerate sloppy code to our master. Kai 2015-09-11 10:19 GMT+02:00 Adrien Nader : > On Fri, Sep 11, 2015, Michel Zou wrote: >> >> You can ping the gcc dudes instead ! >> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67141 > > Considering the issue, I

Re: [Mingw-w64-public] gcc 5.2.1 libgomp testsuite failures with latest runtime and winpthread

Am 09.08.2015 19:17 schrieb Mattias Engdegård matti...@acm.org: 7 aug 2015 kl. 14.50 skrev Rainer Emrich rai...@emrich-ebersheim.de: This fixes the issue, libgom.sum attached. Can we have this in head and in 4.x ? That is probably the expedient solution even if we eventually get libgomp

Re: [Mingw-w64-public] gcc 5.2.1 libgomp testsuite failures with latest runtime and winpthread

7 aug 2015 kl. 14.50 skrev Rainer Emrich rai...@emrich-ebersheim.de: This fixes the issue, libgom.sum attached. Can we have this in head and in 4.x ? That is probably the expedient solution even if we eventually get libgomp fixed. (The patch adds an extra cycle or two on some critical paths

Re: [Mingw-w64-public] gcc 5.2.1 libgomp testsuite failures with latest runtime and winpthread

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Am 06.08.2015 um 23:27 schrieb Mattias Engdegård: 6 aug 2015 kl. 12.46 skrev Rainer Emrich sf.rai...@emrich-ebersheim.de: I assume that's caused by the latest winpthread changes. Sort of; it looks like a bug in libgomp that was tolerated by the

Re: [Mingw-w64-public] gcc 5.2.1 libgomp testsuite failures with latest runtime and winpthread

6 aug 2015 kl. 12.46 skrev Rainer Emrich sf.rai...@emrich-ebersheim.de: Using the x86_64 runtime and winpthread from 4th of August I get a lot of libgomp testsuite failures. Nearly all execution tests fail!!! That's a regression against older runtime/winpthread versions. I assume that's