From: "Martin Liška" <mliska@suse.cz>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Cc: Jakub Jelinek <jakub@redhat.com>
Subject: Re: [PATCH] Implement no_sanitize function attribute
Date: Fri, 06 Jan 2017 15:26:00 -0000 [thread overview]
Message-ID: <089794d6-5aab-696a-eb0d-789ad6f4aec3@suse.cz> (raw)
In-Reply-To: <72103b1d-0119-f05d-043d-ca2edf242bf3@suse.cz>
PING^1
On 12/22/2016 02:38 PM, Martin Liška wrote:
> Hello.
>
> As I previously agreed with Jakub, I prepared patch which adds
> no_sanitize function attribute (same what clang support).
>
> That encompasses following changes:
> 1) all no_sanitize_* function attributes are parsed and stored to no_sanitize_flags
> in DECL_ATTRIBUTES
> 2) instead of flag_sanitize & X, let's call sanitize_flags_p (X), where the DECL_ATTRIBUTES
> are checked within the function
> 3) I prepared many test-cases which test every (almost) single sub-option of UBSAN and all
> functions are decorated with no_sanitize attribute disabling all sanitization except the one
> tested in a particular test
> 4) documentation entry is introduced
>
> Misc changes:
> a) I would like to rename SANITIZE_NONDEFAULT to SANITIZE_UNDEFINED_NONDEFAULT
> b) Documentation fix for -sanitize=bounds-strict is added
>
> Patch can bootstrap on ppc64le-redhat-linux and survives regression tests.
>
> Martin
>
next prev parent reply other threads:[~2017-01-06 15:26 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-22 14:27 Martin Liška
2017-01-06 15:26 ` Martin Liška [this message]
2017-05-31 8:06 ` [PATCH v2] " Martin Liška
2017-05-31 8:35 ` Alexander Monakov
2017-05-31 11:33 ` Martin Liška
2017-05-31 8:38 ` Jakub Jelinek
2017-05-31 11:26 ` Martin Liška
2017-05-31 11:39 ` Jakub Jelinek
2017-05-31 11:51 ` Richard Biener
2017-05-31 11:52 ` Jakub Jelinek
2017-05-31 11:59 ` Martin Liška
2017-05-31 12:04 ` Jakub Jelinek
2017-05-31 12:08 ` Richard Biener
2017-05-31 12:28 ` Martin Liška
2017-06-01 8:03 ` Bernhard Reutner-Fischer
2017-05-31 12:06 ` Richard Biener
2017-05-31 12:37 ` Martin Liška
2017-05-31 13:32 ` Richard Biener
2017-05-31 14:20 ` Martin Liška
2017-06-02 10:40 ` Richard Biener
2017-06-08 13:30 ` Martin Liška
2017-06-08 13:47 ` Jakub Jelinek
2017-06-09 9:29 ` Martin Liška
2017-06-09 9:42 ` Jakub Jelinek
2017-06-09 12:12 ` Martin Liška
2017-06-09 10:12 ` Richard Biener
2017-06-09 10:17 ` Martin Liška
2017-06-09 10:39 ` Richard Biener
2017-06-09 10:49 ` Martin Liška
2017-06-09 11:05 ` Richard Biener
2017-06-09 12:08 ` Martin Liška
2017-06-09 12:27 ` Richard Biener
2017-06-09 12:51 ` Martin Liška
2017-06-09 13:35 ` Richard Biener
2017-06-13 11:10 ` Martin Liška
2017-06-13 13:49 ` Richard Biener
2017-06-13 13:59 ` Martin Liška
2017-05-31 11:57 ` Martin Liška
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=089794d6-5aab-696a-eb0d-789ad6f4aec3@suse.cz \
--to=mliska@suse.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
/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).