On 12/22/2016 11:52 AM, David Wohlferd wrote:
> On 12/21/2016 4:27 AM, JonY wrote:
>> On 12/21/2016 07:29 AM, David Wohlferd wrote:
>>> Comments?  Zidane, can you try this?
>> David, can you also test against the gfortran testsuites?
> 
> Since mingw-w64 doesn't have any gfortran testsuites, I assume you want 
> me to run gcc's.  Running "make -k check-fortran"before applying my fix 
> shows a BUNCH of failures. Since I know squat about fortran, I'm not 
> sure if this is because my environment is set up wrong, or if there are 
> normally this many errors.  My gcc source is also somewhat old.
> 
>> Kai asks to make sure there are no new failures introduced by this change.
> 
> I suppose the most significant metric is how many failures are added (or 
> removed) by applying my patch.  It turns out, the number of failures is 
> unchanged:
> 
>                  === gfortran Summary ===
> 
> # of expected passes            42031
> # of unexpected failures        788
> # of expected failures          80
> # of unsupported tests          180
> 
> Logfile available upon request.
> 
>> Thanks for looking into it.
> 
> What's next?

OK, clear to apply to master, thanks for testing!


Attachment: signature.asc
Description: OpenPGP digital signature

------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/intel
_______________________________________________
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Reply via email to