From: Andrew Donnellan <andrew.donnellan@au1.ibm.com>
To: Emese Revfy <re.emese@gmail.com>, kernel-hardening@lists.openwall.com
Cc: linux-kbuild@vger.kernel.org, pageexec@freemail.hu,
spender@grsecurity.net, mmarek@suse.com, keescook@chromium.org,
linux@rasmusvillemoes.dk, fengguang.wu@intel.com,
dvyukov@google.com, linux-kernel@vger.kernel.org,
david.brown@linaro.org, yamada.masahiro@socionext.com,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Daniel Axtens <dja@axtens.net>
Subject: Re: [kernel-hardening] [PATCH v8 2/4] GCC plugin infrastructure
Date: Thu, 19 May 2016 07:14:58 +1000 [thread overview]
Message-ID: <573CDB52.30701@au1.ibm.com> (raw)
In-Reply-To: <20160518123327.9018f73af78a47b4456b2027@gmail.com>
On 18/05/16 20:33, Emese Revfy wrote:
> Did you test the plugins with all gcc versions (4.5-6)?
No, I tested with 4.8 and 5.2 as those are the toolchains I have on hand
- I'll try to test with the rest of 4.5 - 6.1.
--
Andrew Donnellan OzLabs, ADL Canberra
andrew.donnellan@au1.ibm.com IBM Australia Limited
next prev parent reply other threads:[~2016-05-18 21:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160513015456.01415979f20a68eb7d2d9290@gmail.com>
[not found] ` <20160513015725.30223ee16a2a3860b4392b90@gmail.com>
2016-05-18 8:51 ` [kernel-hardening] [PATCH v8 2/4] GCC plugin infrastructure Andrew Donnellan
2016-05-18 10:33 ` Emese Revfy
2016-05-18 21:14 ` Andrew Donnellan [this message]
2016-05-19 6:22 ` Michael Ellerman
2016-05-19 6:30 ` Andrew Donnellan
2016-05-19 8:24 ` PaX Team
2016-05-20 6:22 ` Andrew Donnellan
2016-05-20 10:10 ` Michael Ellerman
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=573CDB52.30701@au1.ibm.com \
--to=andrew.donnellan@au1.ibm.com \
--cc=david.brown@linaro.org \
--cc=dja@axtens.net \
--cc=dvyukov@google.com \
--cc=fengguang.wu@intel.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mmarek@suse.com \
--cc=mpe@ellerman.id.au \
--cc=pageexec@freemail.hu \
--cc=re.emese@gmail.com \
--cc=spender@grsecurity.net \
--cc=yamada.masahiro@socionext.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 NNTP newsgroup(s).