This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug ipa/67368] Inlining failed due to no_sanitize_address and always_inline conflict
- From: "loic.yhuel at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 04 Oct 2017 16:30:35 +0000
- Subject: [Bug ipa/67368] Inlining failed due to no_sanitize_address and always_inline conflict
- Auto-submitted: auto-generated
- References: <bug-67368-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67368
Loïc Yhuel <loic.yhuel at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |loic.yhuel at gmail dot com
--- Comment #4 from Loïc Yhuel <loic.yhuel at gmail dot com> ---
(In reply to Andrey Ryabinin from comment #3)
> Nope, it was prohibited because no_sanitize_address didn't work for inlined
> function https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59600.
So this case should work : functions inlined into a no_sanitize_address
function would have the sanitizer disabled.
Unlike the opposite, which could crash, this one only could fail to detect
issues at runtime, so perhaps it should only be a warning.