About 'error stop' statement

[Tim Prince via fortran]

This week I was able to build and test gcc trunk on wsl.  Recent Microsoft upgrades appear to help.  There was an out of memory condition (6 GB installed) during gcc testsuite as if memory is leaking.

Sent from my Dell Venue8 with Intel RealSense Snapshot.On Aug 7, 2017 12:56, Damian Rouson <damian@sourceryinstitute.org> wrote:
>
>   
>
>
>
> On August 7, 2017 at 2:08:31 AM, Janne Blomqvist (blomqvist.janne@gmail.com(mailto:blomqvist.janne@gmail.com)) wrote: 
>
> > On Mon, Aug 7, 2017 at 9:59 AM, Angelo Graziosi  
> > wrote:  
> >  
> >  
> > I think the discussion of co-arrays here is entirely irrelevant.  
> > You're not using co-arrays, and no co-array library should be linked  
> > into your binary.  
>
> I agree. FWIW, I asked whether he used the OpenCoarrays installer, not 
> whether he’s using coarrays.  He is using the Windows Subsystem for Linux  
> (which is not yet common) and GCC 5, which matches what the OpenCoarrays  
> requires (WSL) and installs (GCC 5). Also, the use of ERROR STOP seemed 
> like an indication that the submitted code might have been simplified  
> from an application that runs in multiple images (with or without coarrays). 
>
> > What I think you're seeing is  
> >  
> > a) In GCC 6, there is some bug in libbacktrace (the library GFortran  
> > uses to print backtraces) on Windows, causing a segfault. This seems  
> > to have been fixed in GCC 7. (I'm blaming libbacktrace here, because  
> > the GFortran ERROR STOP implementation has not changed between 6 and  
> > 7. Though it could be some other change in the GCC Windows target  
> > support as well, I guess.) 
>
> which is why I’m hoping he’ll solve the issue by upgrading to a newer 
> version of GCC on WSL and share how he managed to do so.  The only way 
> I found to do it was to build GCC from source.  I’m hoping there’s a  
> way to install a newer version of GCC on WSL via package management. 
>
>
> Damian 
>
>