From: "Martin Liška" <mliska@suse.cz>
To: Marco Elver <elver@google.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
Peter Zijlstra <peterz@infradead.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Will Deacon <will@kernel.org>,
"Jose E. Marchesi" <jemarch@gnu.org>,
"Paul E. McKenney" <paulmck@kernel.org>,
Ard Biesheuvel <ardb@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
linux-toolchains@vger.kernel.org
Subject: Re: Linux Plumbers Conf 2021
Date: Thu, 20 May 2021 10:34:13 +0200 [thread overview]
Message-ID: <d52cbb09-d304-af89-f68f-3526e3edb9ff@suse.cz> (raw)
In-Reply-To: <CANpmjNNv+sFDBdZsQsZQ6pUXA1psEqY3phCuHTFrDxruYVKHUA@mail.gmail.com>
On 5/19/21 5:05 PM, Marco Elver wrote:
> On Wed, 19 May 2021 at 17:02, Martin Liška <mliska@suse.cz> wrote:
>> On 5/19/21 4:04 PM, Marco Elver wrote:
>>> +Cc Martin, who helped us last time with no_sanitize issues in GCC.
>>>
>>> Martin, as far as we're aware there's no
>>> __attribute__((no_sanitize_coverage)) for GCC -- is it possible to
>>> implement this? Some context below. Thank you.
>>
>> Yes, I've just implemented the attribute and I'm going to send it to
>> the gcc-patches mailing list tomorrow.
>
> Very nice, thank you!
You're welcome.
The patch has been just sent here:
https://gcc.gnu.org/pipermail/gcc-patches/2021-May/570840.html
Martin
>
> -- Marco
>
next prev parent reply other threads:[~2021-05-20 8:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKwvOdm-Vb2BGRCmtYCh5JcGkM+XedzSMdNr8kQLbY4y_85EvA@mail.gmail.com>
[not found] ` <20210518121447.GB7914@willie-the-truck>
[not found] ` <20210518124311.r4fwv6lfz3erkqnb@treble>
2021-05-18 12:48 ` Linux Plumbers Conf 2021 Josh Poimboeuf
2021-05-18 13:21 ` Peter Zijlstra
2021-05-18 16:57 ` Nick Desaulniers
2021-05-18 20:03 ` Peter Zijlstra
2021-05-18 20:15 ` Nick Desaulniers
2021-05-19 9:32 ` Mark Rutland
2021-05-19 10:19 ` Marco Elver
2021-05-19 11:56 ` Mark Rutland
2021-05-19 14:04 ` Marco Elver
2021-05-19 15:02 ` Martin Liška
2021-05-19 15:05 ` Marco Elver
2021-05-20 8:34 ` Martin Liška [this message]
2021-06-16 23:01 ` Nick Desaulniers
2021-06-24 20:35 ` Nick Desaulniers
2021-06-24 20:37 ` Nick Desaulniers
2021-06-28 17:59 ` Will Deacon
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=d52cbb09-d304-af89-f68f-3526e3edb9ff@suse.cz \
--to=mliska@suse.cz \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=elver@google.com \
--cc=jemarch@gnu.org \
--cc=jpoimboe@redhat.com \
--cc=linux-toolchains@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=ndesaulniers@google.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=will@kernel.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 NNTP newsgroup(s).