https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110432
--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to Sascha Scandella from comment #2) > I think this would also be a solution. Would this then be included in a > future GCC 13.2? Yes (In reply to Iain Sandoe from comment #3) > @Jonathan is there a patch for that proposed solution? No Thinking further about this, maybe we should just do: #if !__has_attribute(__init_priority__) || defined __APPLE__ Because checking in the configure script would still give the wrong answer if libstdc++ is built on macOS using Clang (which is unsupported, but people do the darndest things). So maybe keep it simple and just don't try to use the feature on macOS at all, ever. (In reply to Iain Sandoe from comment #5) > in slower time, we might consider the option of following clang's behaviour > for Darwin (possibly with a warning about the does-not-work-between-tus). I don't understand why one would want to use the attribute only within a single TU, that doesn't seem useful.
