On Thu, Oct 31, 2019 at 10:04 PM Steve Kargl
wrote:
>
> On Thu, Oct 31, 2019 at 09:30:26PM +0200, Janne Blomqvist wrote:
> >
> > I'd personally prefer the current behavior. I.e. just let the
> > underlying OS/libc handle it as it sees fit. No need to invent our own
> > semantics here. Tobias quote
On Thu, Oct 31, 2019 at 09:30:26PM +0200, Janne Blomqvist wrote:
>
> I'd personally prefer the current behavior. I.e. just let the
> underlying OS/libc handle it as it sees fit. No need to invent our own
> semantics here. Tobias quoted the relevant part of the standard, which
> the current impleme
On Thu, Oct 31, 2019 at 7:03 PM Steve Kargl
wrote:
>
> On Thu, Oct 31, 2019 at 05:51:38PM +0100, Tobias Burnus wrote:
> > On 10/31/19 5:42 PM, Steve Kargl wrote:
> > > I suspect the other BSDs also follow posix. I wonder if gfortran
> > > should either apply a mask to the stop code or simply map n
On Thu, Oct 31, 2019 at 05:51:38PM +0100, Tobias Burnus wrote:
> On 10/31/19 5:42 PM, Steve Kargl wrote:
> > I suspect the other BSDs also follow posix. I wonder if gfortran
> > should either apply a mask to the stop code or simply map nonzero
> > values to one of EXIT_FAILURE, SIGQUIT, or SIGABR
On Thu, Oct 31, 2019 at 05:46:38PM +0100, Jakub Jelinek wrote:
> On Thu, Oct 31, 2019 at 09:42:07AM -0700, Steve Kargl wrote:
> > On Thu, Oct 31, 2019 at 05:12:39PM +0100, Tobias Burnus wrote:
> > > At some point, 'call abort()' was changed to 'stop'; this works fine as
> > > long as exit status i
On 10/31/19 5:42 PM, Steve Kargl wrote:
I suspect the other BSDs also follow posix. I wonder if gfortran
should either apply a mask to the stop code or simply map nonzero
values to one of EXIT_FAILURE, SIGQUIT, or SIGABRT. Perhaps,
- exit (code);
+ exit (EXIT_FAILURE);
Or "exit (code > 25
On Thu, Oct 31, 2019 at 09:42:07AM -0700, Steve Kargl wrote:
> On Thu, Oct 31, 2019 at 05:12:39PM +0100, Tobias Burnus wrote:
> > At some point, 'call abort()' was changed to 'stop'; this works fine as
> > long as exit status is != 0. At least on my Linux system, this works
> > until 255. (Which
On Thu, Oct 31, 2019 at 05:12:39PM +0100, Tobias Burnus wrote:
> At some point, 'call abort()' was changed to 'stop'; this works fine as
> long as exit status is != 0. At least on my Linux system, this works
> until 255. (Which matches POSIX, which requires 8 bits.) For "stop 256",
> I get an ex
At some point, 'call abort()' was changed to 'stop'; this works fine as
long as exit status is != 0. At least on my Linux system, this works
until 255. (Which matches POSIX, which requires 8 bits.) For "stop 256",
I get an exit status == 0.
I am not sure whether other systems break earlier, bu
