From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: Announce: rmk's nightly builder gets ARM64 support
Date: Fri, 20 Feb 2015 18:32:30 +0000 [thread overview]
Message-ID: <20150220183230.GP31692@arm.com> (raw)
In-Reply-To: <20150220175931.GL8656@n2100.arm.linux.org.uk>
On Fri, Feb 20, 2015 at 05:59:31PM +0000, Russell King - ARM Linux wrote:
> On Fri, Feb 20, 2015 at 02:04:40PM +0000, Will Deacon wrote:
> > On Fri, Feb 20, 2015 at 01:49:22PM +0000, Fabio Estevam wrote:
> > > On Fri, Feb 20, 2015 at 11:38 AM, Russell King - ARM Linux
> > > <linux@arm.linux.org.uk> wrote:
> > >
> > > > From what I can see, this doesn't _build_ a compiler. It grabs
> > > > gcc-linaro-aarch64-linux-gnu-4.9-2014.08_linux.tar.xz from
> > > > http://releases.linaro.org/14.08/components/toolchain/binaries
> > > > and installs that - which contains a load of binaries.
> > >
> > > That's correct. It uses the pre-built binaries from Linaro.
> >
> > For sources, you can usually just pick up the latest GCC release. For
> > example, 4.9.2 worked for me:
> >
> > ftp://ftp.mirrorservice.org/sites/sourceware.org/pub/gcc/releases/gcc-4.9.2/gcc-4.9.2.tar.bz2
> >
> > I can't recommend using trunk at the moment (i.e. GCC 5), as we hit some
> > issues with the PSCI calling code that I plan to post fixes for at -rc1.
>
> Thanks, that version of gcc appears to work correctly with the kernel.
> I've updated the builder with that.
>
> There's a number of worrying warnings for ldp/stp instructions though.
> Is that a binutils issue, or a KVM issue?
That one's a binutils issue -- it's erroneously aliasing sp and xzr. I filed
a bug internally with our tools team, so it should be fixed soon.
> I've sent Greg a fix for the drivers/base/component.c warning.
>
> There's a number of warnings in drivers/pci/host/pci-xgene.c which
> look like they need resolving - returning NULL from a function which
> returns an 'int' has never been valid - has this commit (which seems
> to have introduced the problem) actually been tested?
Yeah, I noticed those but haven't dug into them yet (I also don't have
an xgene).
Will
next prev parent reply other threads:[~2015-02-20 18:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-19 17:12 Announce: rmk's nightly builder gets ARM64 support Russell King - ARM Linux
2015-02-19 18:34 ` Russell King - ARM Linux
2015-02-20 9:20 ` Will Deacon
2015-02-20 9:24 ` Ard Biesheuvel
2015-02-20 9:40 ` Russell King - ARM Linux
2015-02-20 10:20 ` Russell King - ARM Linux
2015-02-20 10:35 ` Fabio Estevam
2015-02-20 13:38 ` Russell King - ARM Linux
2015-02-20 13:49 ` Fabio Estevam
2015-02-20 14:03 ` Ard Biesheuvel
2015-02-20 14:04 ` Will Deacon
2015-02-20 17:59 ` Russell King - ARM Linux
2015-02-20 18:02 ` Fabio Estevam
2015-02-20 18:08 ` Marc Zyngier
2015-02-20 18:32 ` Will Deacon [this message]
2015-02-20 22:12 ` Rob Herring
2015-02-20 19:03 ` Robert Schwebel
2015-02-20 11:45 ` Jeremy Kerr
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=20150220183230.GP31692@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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.