https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65873
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- (In reply to Jan Hubicka from comment #1) > I think certain combinations of flag will trigger ICE, such as one > enabling/disabling vector builtins. But I suppose we may want to bypass > majority of the checks for case we have always_inline w/o explicit > optimization attribute indeed, but only at early inlining time, probably not > at LTO? > At LTO time we already did transformation that turn previously correct code > with target's optimization flags to be incorrect (i.e. -fstrict-aliasing > blocks some transformations we may do during early opts) Yeah, special casing always_inline with no explicit optimize/target attributes only, and only during early inlining IMHO should be sufficient.
