https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113341
--- Comment #15 from Segher Boessenkool <segher at gcc dot gnu.org> --- (In reply to Jessica Clarke from comment #8) > The clang/ subdirectory should be building itself with -fno-strict-aliasing > on GCC already "Should". I guess you mean "is", as in "we already concluded we have a big fat bug here"? I would expect the code to be valid C (or C++). So that option should never be needed. This command line flag means "my code violates many of the principles of C, but try to compile it anyway, even although I have no clue what I am doing there, and you cannot know what I meant either, obviously".