From: "Lucas, Philipp" <philipp.lucas@siemens.com>
To: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Prevent sanitization also for inlined functions
Date: Wed, 18 May 2022 13:28:23 +0000 [thread overview]
Message-ID: <DB9PR10MB57402D1A42610CF630CEF6C6EDD19@DB9PR10MB5740.EURPRD10.PROD.OUTLOOK.COM> (raw)
[-- Attachment #1: Type: text/plain, Size: 544 bytes --]
Hello,
I wish to sanitize a large codebase except for a certain set of
time-critical functions. To this end, I globally set the flag
-fsanitize=undefined and annotate the functions which should not be
sanitized with a __no_sanitize_undefined__ attribute.
Unfortunately, it seems that sanitization is performed before inlining,
so that despite the annotations, the functions include instrumentation
of the inlined functions (https://godbolt.org/z/b5qoqTYvE ).
Is there any way to prevent that?
--
Philipp Lucas
philipp.lucas@siemens.com
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 14895 bytes --]
reply other threads:[~2022-05-18 13:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DB9PR10MB57402D1A42610CF630CEF6C6EDD19@DB9PR10MB5740.EURPRD10.PROD.OUTLOOK.COM \
--to=philipp.lucas@siemens.com \
--cc=gcc-help@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).