Please Review
diff --git a/mingw-w64-headers/crt/math.h b/mingw-w64-headers/crt/math.h
index 069e734..0d27e85 100644
--- a/mingw-w64-headers/crt/math.h
+++ b/mingw-w64-headers/crt/math.h
@@ -207,7 +207,7 @@ extern "C" {
#if !defined (__ia64__)
__CRT_INLINE float __cdecl fabsf (float x)
{
-#
The scanf functions don't specify thumb mode which makes them fail to
compile.
Please Review
diff --git a/mingw-w64-crt/stdio/vfscanf2.S b/mingw-w64-crt/stdio/vfscanf2.S
index f6ba5d6..97807a9 100644
--- a/mingw-w64-crt/stdio/vfscanf2.S
+++ b/mingw-w64-crt/stdio/vfscanf2.S
@@ -9,6 +9,9 @@
#defi
On 8/4/2015 18:35, Jacek Caban wrote:
> On 08/04/15 02:02, JonY wrote:
>> Patch OK?
>
> Looks good to me.
>
Done.
0xD4EBC740.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature
---
Hi,
Consider such code:
*
{
pthread_spinlock_t* lock_pointer;
pthread_spinlock_t lock_value;
lock_pointer = (pthread_spinlock_t*)calloc( 1,
sizeof(pthread_spinlock_t) );
pthread_spin_init( lock_pointer, 0 );
lock_value = *lock_pointer; /* == -1 */
free( lock_pointer );
**
6 aug 2015 kl. 12.46 skrev Rainer Emrich :
> 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 caused by the latest winpthr
Dear all,
I use mingw-w64 under Lubuntu Linux. I try to compile with mingw-w64, 32
bits:
/usr/bin/i686-w64-mingw32-g++ -std=c++0x -isystem
/usr/lib/gcc/i686-w64-mingw32/4.8 -isystem /usr/i686-w64-mingw32/include
-isystem /usr/share/mingw-w64/include -Wshadow -DWINVER=0x0500
-D_WIN32_WINNT=0x0500
Am 06.08.2015 um 15:37 schrieb JonY:
> On 8/6/2015 20:08, xantares 09 wrote:
>> hi, are there any known issues regarding openmp with this new release ?
>> when upgrading from 4.0.2 to 4.0.4, i cannot run an openmp test case any
>> more: err:module:attach_process_dlls "libgomp-1.dll" failed to
>> i
From: xantare...@hotmail.com
To: mingw-w64-public@lists.sourceforge.net
Date: Thu, 6 Aug 2015 13:44:35 +
Subject: Re: [Mingw-w64-public] v4.0.4 openmp issue
Date: Thu, 6 Aug 2015 21:37:50 +0800
From: jo...@users.sourceforge.net
To: mingw-w64-public@lists.sourceforge.net
Subject: Re: [Mi
Date: Thu, 6 Aug 2015 21:37:50 +0800
From: jo...@users.sourceforge.net
To: mingw-w64-public@lists.sourceforge.net
Subject: Re: [Mingw-w64-public] v4.0.4 openmp issue
On 8/6/2015 20:08, xantares 09 wrote:
> hi,
> are there any known issues regarding openmp with this new release ?
> when upgrading
On 8/6/2015 20:08, xantares 09 wrote:
> hi,
> are there any known issues regarding openmp with this new release ?
> when upgrading from 4.0.2 to 4.0.4, i cannot run an openmp test case any more:
> err:module:attach_process_dlls "libgomp-1.dll" failed to initialize, aborting
> with the same version
hi,
are there any known issues regarding openmp with this new release ?
when upgrading from 4.0.2 to 4.0.4, i cannot run an openmp test case any more:
err:module:attach_process_dlls "libgomp-1.dll" failed to initialize, aborting
with the same version of wine, same gcc 5.2.0 for i686-w64-mingw32 tar
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 caused by the latest winpthread changes.
Any comments? Kai?
Cheers
Rainer
Mateusz 2015-08-05 23:54:
> There are wrong folders:
> in "Toolchains targetting Win32/" there are "sjlj" & "seh" instead of
> "sjlj" & "dwarf"
Hi,
My fault, sorry.
Fixed.
--
13 matches
Mail list logo