[Bug preprocessor/48839] #error should terminate compilation - similar to missing #include

[redi at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48839

--- Comment #11 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Paolo Carlini from comment #8)
> about the other compilers? For sure some are following the current gcc
> behaviour, for compatibility, I suspect ICC for example. Should we also have
> a command line switch? Probably missing #includes just unconditionally end
> the compilation on most compilers, though. Well, it's also true that the so
> called workaround which I mentioned in Comment #1 works pretty well and we
> do have *very* few fatal errors in the front ends...

Clang keeps going, like GCC. ICC seems to as well.

But EDG stops immediately with a "catastrophic error":

"foo.cc", line 1: catastrophic error: #error directive: NOPE


Anyway, I don't think compatibility is an issue. We're not going to produce any
assembly or other output, compilation fails.