https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67368
--- Comment #2 from Yury Gribov <y.gribov at samsung dot com> --- (In reply to Richard Biener from comment #1) > so it fails on purpose (not sure why though). And it ignores always-inline. > I wonder if we should, for always-inline functions, inline anyway and output > a warning instead. We prohibited this combination during ASan integration to kernel. Both always_inline and no_sanitize_address are strong requirements for compiler i.e. dropping any of these in favor of another would have unexpected effects and hurt usability.
