https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119590
--- Comment #4 from Iain Sandoe <iains at gcc dot gnu.org> --- (In reply to Jakub Jelinek from comment #3) > So something fixincludes should fix? looks like another case where having a single FE for c-family makes it easy to mistakenly accept C in C++ and vice versa At the moment, I am very reluctant to add more fixincludes, since the SDKs are changing fast, which gives us other problems in maintaining stability - I'll take a look at what we might do as another "clang compatibility" extension for Darwin - if that proves too hard than we might have to fall back to fixincludes. Unless it repeats somehow with x86_64 (which I will check later)... then this probably belongs as an issue against the aarch64-darwin devt branch.
