https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120299
--- Comment #12 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to Tymi from comment #4) > Why not check for __clang__ and fallback to a compatible solution then? Because that should only ever be a last resort. The right way to do it is write portable code that depends on which features are supported by the compiler, not what the compiler's name is.
