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

--- Comment #10 from Jonathan Wakely <redi at gcc dot gnu.org> ---
I don't think we want the compiler to notice whether a header depends on any
macros, and then mark it for not being translated to import (either
unconditionally or if those macros are defined). 99.999% of headers depend on
macros (of nothing else, the include guard at the very top of the header!) and
many depend on macros which are routinely defined, such as:

#ifdef __linux__

#ifdef __cpp_concepts

We don't want to make a header non-importable just because it uses #ifdef
anywhere in the header.

Recording _which_ macros a header depends on and testing that all of them have
the same definition before doing include translation would work but I'm not
sure how well it would scale.

Reply via email to