All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Breeds <tony@bakeyournoodle.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Kees Cook <keescook@google.com>,
	Paul Gortmaker <paul.gortmaker@windriver.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Arnd Bergmann <arnd@arndb.de>,
	Randy Dunlap <rdunlap@infradead.org>,
	Olof Johansson <olof@lixom.net>, Mark Brown <broonie@kernel.org>,
	info@kernelci.org, Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Will Deacon <will.deacon@arm.com>,
	Russell King - ARM Linux <linux@arm.linux.org.uk>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux-Next <linux-next@vger.kernel.org>,
	Fengguang Wu <fengguang.wu@intel.com>,
	Andrew Donnellan <andrew.donnellan@au1.ibm.com>,
	Laura Abbott <labbott@redhat.com>,
	"x86@kernel.org" <x86@kernel.org>
Subject: Re: enabling COMPILE_TEST support for GCC plugins in v4.11
Date: Sat, 24 Jun 2017 07:16:03 +1000	[thread overview]
Message-ID: <20170623211603.GD28216@thor.bakeyournoodle.com> (raw)
In-Reply-To: <871sqbqmw1.fsf@concordia.ellerman.id.au>

[-- Attachment #1: Type: text/plain, Size: 2045 bytes --]

On Fri, Jun 23, 2017 at 03:43:58PM +1000, Michael Ellerman wrote:
> [Old thread just popped up in my inbox]
> 
> Kees Cook <keescook@google.com> writes:
> > On Thu, Dec 8, 2016 at 5:52 PM, Paul Gortmaker
> > <paul.gortmaker@windriver.com> wrote:
> >> On Thu, Dec 8, 2016 at 2:00 PM, Kees Cook <keescook@google.com> wrote:
> >>> Hi,
> >>>
> >>> I'd like to get the GCC plugins building under
> >>> allyesconfig/allmodconfig for -next soon (with the intention of
> >>> landing the change in v4.11). Specifically, I intend to revert
> >>> a519167e753e ("gcc-plugins: disable under COMPILE_TEST").
> >>
> >> If I recall correctly, I noted that the plugins broke the kernel.org
> >> cross compiler toolchains which led to the above disable.
> >
> > Do you mean these?
> > https://www.kernel.org/pub/tools/crosstool/
> 
> I think those are the ones Paul is talking about.
> 
> Those were mostly built by Tony, who is know, sadly, an Openstack
> developer and for some reason doesn't seem to have time to build
> toolchains for kernel hackers :P

Yeah sad but true.  Building a full suit took a couple of days and I'm
just not going to find that anytime soon.

I don't really want to build them one at a time but I could I suppose,
I'd play favotites x64_86, ppc64le and then the others if and when time
becomes an option.  My problem with that is it kinda defeats the aim on
why I put th etoolchains up there.  to enable testing accross the range
of architectures in a consistent way.

Another option would clearly be to find someone that is closer to the
kernel to do this thing.

Ho hum thoughts?

> As folks may have seen on LWN, there are now pre-built toolchains for
> many architectures available from the Free Electrons guys, so that may
> help to unblock this situation somewhat:
> 
> http://toolchains.free-electrons.com/

So ubuntu and Fedora each have cross toolschains in the distro and we
that those ^^.  Perhaps this no longer needs to be provided by the
kernel community?

Yours Tony.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2017-06-23 21:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-08 19:00 enabling COMPILE_TEST support for GCC plugins in v4.11 Kees Cook
2016-12-09  1:52 ` Paul Gortmaker
2016-12-09  4:15   ` Kees Cook
2017-06-23  5:43     ` Michael Ellerman
2017-06-23  5:43       ` Michael Ellerman
2017-06-23 18:35       ` Kees Cook
2017-06-23 21:16       ` Tony Breeds [this message]
2016-12-09 10:40 ` Arnd Bergmann
2016-12-09 19:12   ` Kees Cook
2016-12-09 19:40     ` Linus Torvalds
2017-06-23  0:18       ` Kees Cook
2016-12-10 16:45     ` Emese Revfy
2016-12-16 21:05       ` Kees Cook
2016-12-09 11:33 ` Arnd Bergmann
2016-12-09 19:13   ` Kees Cook
2016-12-09 20:35     ` Arnd Bergmann
2016-12-09 21:08       ` kugan

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=20170623211603.GD28216@thor.bakeyournoodle.com \
    --to=tony@bakeyournoodle.com \
    --cc=akpm@linux-foundation.org \
    --cc=andrew.donnellan@au1.ibm.com \
    --cc=arnd@arndb.de \
    --cc=broonie@kernel.org \
    --cc=fengguang.wu@intel.com \
    --cc=info@kernelci.org \
    --cc=keescook@google.com \
    --cc=labbott@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mpe@ellerman.id.au \
    --cc=olof@lixom.net \
    --cc=paul.gortmaker@windriver.com \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.org \
    --cc=will.deacon@arm.com \
    --cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.