https://gcc.gnu.org/bugzilla/show_bug.cgi?id=121741
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> --- We can certainly use always_inline in some functions, but I don't think we want it for everything that contains a hardened assertion. So maybe we could use either always_inline or abi_tag on all hardened functions. Or we can do nothing and expect users to build with consistent flags if they want hardening ... but we'll get blamed when they don't do it. The rules in the C++26 draft talk about a hardened implementation, not being able to pick and choose per-TU.
