https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89864
--- Comment #70 from Iain Sandoe <iains at gcc dot gnu.org> --- (In reply to Jürgen Reuter from comment #69) > (In reply to Iain Sandoe from comment #68) > > Created attachment 46176 [details] > > revised fixincludes patch. > > > > The patch attached include the generated files, and I'd be grateful if folks > > would test it (right now I have limited access to Darwin test boxen, but it > > seems to DTRT for me) - I will post to @patches, but leave commit until it's > > confirmed that it's working. > > I will test this fix tonight when I have access to enough electricity again. > > It looks like this really affects things, I am not clear what you're reporting here - the patch will not "do anything" until you build GCC with it applied, and then install the built compiler. > as my try to compile LLVM failed: Does this mean, "when building LLVM on OSX 10.14.2 using GCC as the bootstrap compiler"? (I'm not sure what's wrong here - if the compiler bootstrap succeeds, then the compiler should be able to process the headers - if the code is C11, then _Atomic should be accepted, if it's C++ then _Atomic should be mapped to volatile).