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

Eric Gallager <egallager at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |DUPLICATE
                 CC|                            |egallager at gcc dot gnu.org

--- Comment #2 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to valsiterb from comment #0)
> I was working on a 20 years old codebase and in order to increase
> compilation speed, I've converted all header guards to #ifdef ... #error to
> go on and change things around, but there was a cycle somewhere in the
> headers (a.h includes b.h but b.h also includes a.h) cpp does not detect
> this case and goes on unil it gets killed.
> I don't know if cycle detection is even supposed to part of the
> preprocessor, but I expected that #error would make it stop there. I know
> that there is -Wfatal-errors directive. Shouldn't #error be be fatal or am I
> missing something?

This is bug 48839; closing this as a dup of that.

*** This bug has been marked as a duplicate of bug 48839 ***

Reply via email to