Re: [PATCH, libgfortran] PR 61310 CTIME intrinsic output incorrect on MinGW

2014-05-26 Thread Steve Kargl
On Mon, May 26, 2014 at 01:00:56PM +0300, Janne Blomqvist wrote: > On Mon, May 26, 2014 at 1:25 AM, Steve Kargl > wrote: > > On Mon, May 26, 2014 at 12:21:21AM +0300, Janne Blomqvist wrote: > >> Hi, > >> > >> GFortran currently uses strftime(...,"%c",...) to produce the result > >> for the CTIME a

Re: [PATCH, libgfortran] PR 61310 CTIME intrinsic output incorrect on MinGW

2014-05-26 Thread Janne Blomqvist
On Mon, May 26, 2014 at 1:25 AM, Steve Kargl wrote: > On Mon, May 26, 2014 at 12:21:21AM +0300, Janne Blomqvist wrote: >> Hi, >> >> GFortran currently uses strftime(...,"%c",...) to produce the result >> for the CTIME and FDATE intrinsics. Unfortunately, it seems that on >> MinGW this does not pro

Re: [PATCH, libgfortran] PR 61310 CTIME intrinsic output incorrect on MinGW

2014-05-25 Thread Steve Kargl
On Mon, May 26, 2014 at 12:21:21AM +0300, Janne Blomqvist wrote: > Hi, > > GFortran currently uses strftime(...,"%c",...) to produce the result > for the CTIME and FDATE intrinsics. Unfortunately, it seems that on > MinGW this does not produce identical output to the C stdlib ctime(), > even in th

[PATCH, libgfortran] PR 61310 CTIME intrinsic output incorrect on MinGW

2014-05-25 Thread Janne Blomqvist
Hi, GFortran currently uses strftime(...,"%c",...) to produce the result for the CTIME and FDATE intrinsics. Unfortunately, it seems that on MinGW this does not produce identical output to the C stdlib ctime(), even in the default locale. The attached patch implements an alternative approach, ori