dalias added a comment. To be clear, musl does not support this regardless of whether `#include_next` is being used "right" or not. The only supported thing is not mixing headers at all.
If Emscripten and wasi are using musl-based headers, it probably makes sense for these targets to do the same thing with include order as for musl targets. The practice of mixing responsibility for system headers between libc and the compiler is a very glibc+gcc specific legacy thing. Even on gcc, the BSD targets don't do this. Other targets might just because the gcc folks had a thing about "fixing" proprietary unices' headers, but the standard open source non-GNU thing to do is to leave the headers entirely as the libc's responsibility. Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D159383/new/ https://reviews.llvm.org/D159383 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
