[Bug ipa/65873] [5/6 Regression] Failure to inline always_inline memcpy
hubicka at gcc dot gnu.org
Mon Apr 27 08:05:00 GMT 2015
--- Comment #1 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
The diff in flags is the following:
not inlinable: bar/1 -> memcpy/0, optimization level attribute mismatch
so we fail because of errno-math difference.
The logic accepting/rejecitng inlines in can_inline_edge_p and I guess it is
the fact that we are affraid to inline safe math to unsafe.
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)
More information about the Gcc-bugs