From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] drivers: SPI: sunxi SPL: fix warning
Date: Mon, 14 Nov 2016 15:12:09 -0500 [thread overview]
Message-ID: <20161114201209.GO27304@bill-the-cat> (raw)
In-Reply-To: <91683a9a-6f16-21dc-4295-d49f35acfce6@arm.com>
On Mon, Nov 14, 2016 at 07:43:40PM +0000, Andr? Przywara wrote:
[snip]
> On a related matter, I ran buildman on HEAD for armv8 today and GCC 6.2
> found quite some issues (will send out the fixes ASAP).
> So is there some buildbot somewhere that runs buildman? If yes, with
> what compilers?
What gcc-6.2 compilers are you using? The travis-ci setup is using the
Ubuntu 'Trusty' compilers, which are not that recent. I also have been
running debian/unstable in a chroot, but it's old enough of a copy to be
using gcc-5.3.1 currently. I'm going to kick off a new debootstrap
now'ish to see what toolchain versions I can get there. Do you know if
these gcc-6.2 problems you see would also show up for rpi3 in 64bit
mode? That's my current easiest test platform for aarch64. Thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20161114/d9cf91c9/attachment.sig>
next prev parent reply other threads:[~2016-11-14 20:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 0:58 [U-Boot] [PATCH] drivers: SPI: sunxi SPL: fix warning Andre Przywara
2016-11-13 18:48 ` Hans de Goede
2016-11-14 16:30 ` Jagan Teki
2016-11-14 16:47 ` Andre Przywara
2016-11-14 16:56 ` Tom Rini
2016-11-14 18:18 ` Siarhei Siamashka
2016-11-14 18:32 ` Siarhei Siamashka
2016-11-14 19:43 ` André Przywara
2016-11-14 20:12 ` Tom Rini [this message]
2016-11-15 10:48 ` Andre Przywara
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=20161114201209.GO27304@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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.