Re: [Mingw-w64-public] [PATCH 1/2] time.h: Ensure that _POSIX_THREAD_SAFE_FUNCTIONS is defined if we declare *_r functions.

But you could be 100% correct and it might very well be a good move. I'm just not sure to be honest :D On Tue, Feb 3, 2015 at 5:16 PM, Martell Malone wrote: > The _POSIX_THREAD_SAFE_FUNCTIONS Guard is only there for backwards > compatibility with programs that assume the functions are available

Re: [Mingw-w64-public] [PATCH 1/2] time.h: Ensure that _POSIX_THREAD_SAFE_FUNCTIONS is defined if we declare *_r functions.

The _POSIX_THREAD_SAFE_FUNCTIONS Guard is only there for backwards compatibility with programs that assume the functions are available if pthread defines them, that's why there is an || separator Not sure if we should force it to be defined as that should be done by pthread ?? On Tue, Feb 3, 2015

Re: [Mingw-w64-public] [PATCH 1/2] time.h: Ensure that _POSIX_THREAD_SAFE_FUNCTIONS is defined if we declare *_r functions.

Thanks for taking care. Please apply. Thanks, Kai 2015-02-03 12:25 GMT+01:00 Jacek Caban : > This seems logical that if we provide those, we should define it. That's > also a clean way for applications to test for > _POSIX_THREAD_SAFE_FUNCTIONS to detect presence of related functions. > > --- >

Re: [Mingw-w64-public] [PATCH 2/2] intrin-impl.h: Removed not needed __MINGW_EXTENSION.

Patch is ok. Thanks, Kai 2015-02-03 12:25 GMT+01:00 Jacek Caban : > --- > mingw-w64-headers/include/psdk_inc/intrin-impl.h | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > > > -- > Dive into the World of P

Re: [Mingw-w64-public] gfortran, open mp and floating point precision

Hi, 2015-02-03 4:25 GMT+01:00 K. Frank : > Hi Carl (and Pieter)! > > On Mon, Feb 2, 2015 at 5:29 PM, Carl Kleffner > wrote: > > The Windows ABI - see > https://msdn.microsoft.com/en-us/library/ms235286.aspx > > - differes from the > > System V ABI - see http://www.x86-64.org/documentation/abi.pd

Re: [Mingw-w64-public] [Patch] - Hardening libssp against malicious local processes

On 3. 2. 2015 11:53, Georg Koppen wrote: > I am putting a patch inline (not sure if attachments are allowed on this > mailing list) that does not make it possible for a local process anymore > to replace canaries which in turn might disable SSP. Comments and/or > review are much appreciated. > > T

[Mingw-w64-public] [PATCH 2/2] intrin-impl.h: Removed not needed __MINGW_EXTENSION.

--- mingw-w64-headers/include/psdk_inc/intrin-impl.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/mingw-w64-headers/include/psdk_inc/intrin-impl.h b/mingw-w64-headers/include/psdk_inc/intrin-impl.h index 71d6096..1a202f8 100644 --- a/mingw-w64-headers/include/psdk_inc/i

[Mingw-w64-public] [PATCH 1/2] time.h: Ensure that _POSIX_THREAD_SAFE_FUNCTIONS is defined if we declare *_r functions.

This seems logical that if we provide those, we should define it. That's also a clean way for applications to test for _POSIX_THREAD_SAFE_FUNCTIONS to detect presence of related functions. --- mingw-w64-headers/crt/time.h | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git

[Mingw-w64-public] [Patch] - Hardening libssp against malicious local processes

Hi, I am putting a patch inline (not sure if attachments are allowed on this mailing list) that does not make it possible for a local process anymore to replace canaries which in turn might disable SSP. Comments and/or review are much appreciated. The problem it is trying to solve is outlined in

[Mingw-w64-public] [URGENT] Project _and_ tutors for GSoC 2015

Hi, The deadline for organizations is only a few days ahead and if we want mingw-w64 to take part in it, we need to do it _now_. There are some project ideas at http://mingw-w64.sourceforge.net/contribute.php This is by no mean an exhaustive list but at least it's a start. GSoC needs something