9.10.5 Options about halting for warnings

--halt-at-warn

This option causes the compiler to treat all warnings as if they were errors when intending to generate target code. This means that if the compiler issues any warnings, it will not generate target code; instead, it will return a non-zero exit status.

--halt-at-warn-make-interface

--halt-at-warn-make-int

This option causes the compiler to treat all warnings as if they were errors when intending to generate an interface file (a .int, .int0, .int2 or .int3 file). This means that if the compiler issues any warnings at that time, it will not generate the interface file; instead, it will return a non-zero exit status.

--halt-at-warn-make-opt

This option causes the compiler to treat all warnings as if they were errors when intending to generate an optimization file (a .opt or .trans_opt file.) This means that if the compiler issues any warnings at that time, it will not generate the optimization file; instead, it will return a non-zero exit status.

--halt-at-syntax-errors

This option causes the compiler to halt immediately, without doing any semantic checking, if it finds any syntax errors in the program.

--no-halt-at-invalid-interface

This option operates when the compiler is invoked with the ‘--make--interface’ option to generate .int and .int2 files for one or more modules. In its default setting, ‘--halt-at-invalid-interface’, it causes the compiler to check the consistency of those parts of each of those modules that are intended to end up in the .int and .int2 files. If these checks find any problems, the compiler will print an error message for each problem, but will then stop.

Users can prevent this stop, and thus allow the generation of invalid interface files, by specifying ‘--no-halt-at-invalid-interface’. (In this case, the problems in the invalid information files will be reported when compiling the modules that import them.)