This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Another exit codes question
- To: Zack Weinberg <zackw at standford dot edu>
- Subject: Re: Another exit codes question
- From: Chris Reedy <chrisreedy at alum dot mit dot edu>
- Date: Wed, 07 Mar 2001 11:32:49 -0500
- CC: gcc at gcc dot gnu dot org
On Fri, 2 Mar 2001 10:09:57 -0800, Zack Weinberg wrote:
> Right. The existing definitions for SUCCESS_EXIT_CODE and
> FATAL_EXIT_CODE on VMS are [snip]
>
> On the i370 triples, it's
>
> #define SUCCESS_EXIT_CODE 0
> #define FATAL_EXIT_CODE 12
>
> What I'm trying to find out is whether we can rely on the system-
> provided definitions of EXIT_SUCCESS and EXIT_FAILURE on these systems
> rather than know what they have to be ourselves. I'm fairly sure that
> vax-vms is a pre-C89 host, but alpha-vms shouldn't be, and I don't
> know anything about mainframes. (Well, presumably i370-*-linux uses
> the Unix "nonzero is error" convention, which means FATAL_EXIT_CODE of
> 12 is odd but harmless.)
Since no one rose to the occassion:
IBM OS/370, etc. exit codes for compilers are:
0 - Success
4 - Compiled with Warnings
8 - Compiled with Errors (still produces object code)
12 - Failed to Compile (no object code)
16 - Compiler Failed
So the codes given look correct for i370-*-mvs. Can't say about the
other two.
Chris