Re: `--syntax-only' after error

[craig at jcb-sc dot com]

>I agree. But I wasn't talking about this option, but rather about the
>syntax-only option. I do agree with you that having an option to abort
>after the first error might be useful to have, even though I personally
>will probably never use it.

The -fsyntax-only option already exists and is supported, though in
the current sources (1.2) it causes the compiler to crash for some
sources (on my to-do list to fix).  I think you might be confused
by the subject header -- which actually refers to the idea of
turning on -fsyntax-only (mispelled in the header) partway through
the compilation, when the first error message is printed, to do less
work during the rest of the compile (which also means not printing
certain kinds of diagnostics, including potentially useful warnings,
later on -- e.g. unitialized-variable and asm-related diagnostics).

The proposed change(s) and option(s) seem to have died for
lack of both interest and consensus.  I'm happy enough with that
-- well, personally, I'd probably never have used the different
behavior anyway, but I mean I think that's the best approach for
gcc at this time, to do nothing (except fix the -fsyntax-only bug).

        tq vm, (burley)