linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "PaX Team" <pageexec@freemail.hu>
To: Emese Revfy <re.emese@gmail.com>,
	kernel-hardening@lists.openwall.com,
	Michael Ellerman <mpe@ellerman.id.au>
Cc: Andrew Donnellan <andrew.donnellan@au1.ibm.com>,
	linux-kbuild@vger.kernel.org, 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>,
	Daniel Axtens <dja@axtens.net>
Subject: Re: [kernel-hardening] [PATCH v8 2/4] GCC plugin infrastructure
Date: Thu, 19 May 2016 10:24:13 +0200	[thread overview]
Message-ID: <573D782D.10392.75A275C@pageexec.freemail.hu> (raw)
In-Reply-To: <1463638931.10451.10.camel@ellerman.id.au>

On 19 May 2016 at 16:22, Michael Ellerman wrote:

> On Wed, 2016-05-18 at 12:33 +0200, Emese Revfy wrote:
> > Did you test the plugins with all gcc versions (4.5-6)?
> 
> What's the concern about gcc versions? Just not breaking the build on old
> compilers?

the earlier plugin capable gcc versions used to install gcc headers in a somewhat
ad-hoc manner resulting in compile time breakage for plugins and since some of
those potentially missing headers are target specific, each target arch should
be verified before enabling plugin support on them. things have much improved with
gcc 5 (see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61176) though there's still
an occasional missing header but with wider use of plugins they will hopefully be
discovered earlier now. perhaps linux-arch should be cc'ed on the plugin infrastructure
so that arch maintainers are aware of this?

> I'm pretty sure powerpc big endian still builds with gcc 4.4.
> 
> However if Andrew's only tested on little endian, then that select should be
> guarded with an "if CPU_LITTLE_ENDIAN". And to build LE you need gcc >= 4.9.

i guess that's part of the target tuple so in general arch maintainers should test
the target tuples used on their arch with all the supported gcc versions (speaking
of CC, not HOSTCC/HOSTCXX).

cheers,
 PaX Team

  parent reply	other threads:[~2016-05-19  8:48 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
2016-05-19  6:22       ` Michael Ellerman
2016-05-19  6:30         ` Andrew Donnellan
2016-05-19  8:24         ` PaX Team [this message]
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=573D782D.10392.75A275C@pageexec.freemail.hu \
    --to=pageexec@freemail.hu \
    --cc=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=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).