From: Heiko Stuebner <heiko@sntech.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/3] rockchip: rk3188: Add Radxa Rock board
Date: Tue, 04 Apr 2017 19:06:42 +0200 [thread overview]
Message-ID: <1602950.dsGQW7ubfg@phil> (raw)
In-Reply-To: <20170404162953.GG19897@bill-the-cat>
Am Dienstag, 4. April 2017, 12:29:53 CEST schrieb Tom Rini:
> On Fri, Mar 31, 2017 at 10:24:07PM -0600, Simon Glass wrote:
> > On 26 March 2017 at 16:38, Heiko Stuebner <heiko@sntech.de> wrote:
> > > I've added Tom for comments, executive summary:
> > > - rk3188-tpl is size limited to 1020 bytes
> > > - gcc 6.3 produces a rk3188-tpl of 792 bytes
> > > - gcc 4.9 makes it 1020 bytes
> > > - buildman seems to always use gcc-4.9
> > > - rk3188 board does not compile with buildman
> > >
> > >
> > > Isn't holding on to a pretty old compiler for everything somewhat
> > > strange? ;-)
> >
> > Well it's not that old. 4.6 would be old. We do need to be careful not
> > to drop old toolchains too aggressively, although for new platforms
> > such as this is doesn't matter. I try to test with older things to
> > avoid problems applying things to mainline (with Tom's automated
> > tests, etc.)
>
> wrt buildman using certain toolchains, it comes down to the order in
> which it finds matches for a given arch and then it picks (and I don't
> recall which off the top of my head) the first or last match.
>
> I do agree that gcc-4.9 isn't something we can drop just yet (as for
> example it's what'll be used in travis-ci today. But it's getting
> pretty long in the tooth and we will have to at some point say that
> "platform X requires gcc-6.x or later" as we start running into hard
> walls that are solved in 6.x.
>
> Finally, I have no objection to adding TPL_USE_ARCH_MEMSET as an option
> so that in cases like this it can be disabled due to space just as it is
> on SPL.
The problem wasn't ARCH_MEMSET - which already was way outsize the size
constraints, but the general memset also being somewhat big, with its
slight speed optimizations.
But thanks to Simon's recent patches [0] we got a really nice size-
reduction on the Rock's TPL (from 1020 to 488 bytes) . So with these
we're really good with all toolchains now.
Heiko
[0] https://www.mail-archive.com/u-boot at lists.denx.de/msg243443.html
next prev parent reply other threads:[~2017-04-04 17:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 23:41 [U-Boot] [PATCH 0/3] rockchip: rk3188 fixed early stage and radxarock board Heiko Stuebner
2017-03-23 23:41 ` [U-Boot] [PATCH 1/3] rockchip: rk3188: enable TPL_LIBGENERIC for generic memset Heiko Stuebner
2017-03-26 2:40 ` Simon Glass
2017-03-23 23:41 ` [U-Boot] [PATCH 2/3] rockchip: rk3188: Add Radxa Rock board Heiko Stuebner
2017-03-26 2:39 ` Simon Glass
2017-03-26 19:06 ` Heiko Stuebner
2017-03-26 19:59 ` Simon Glass
2017-03-26 20:00 ` Simon Glass
2017-03-26 20:13 ` Heiko Stuebner
2017-03-26 20:41 ` Heiko Stuebner
2017-03-26 20:52 ` Heiko Stuebner
2017-03-26 21:00 ` Heiko Stuebner
2017-03-26 21:28 ` Simon Glass
2017-03-26 22:38 ` Heiko Stuebner
2017-04-01 4:24 ` Simon Glass
2017-04-04 16:29 ` Tom Rini
2017-04-04 17:06 ` Heiko Stuebner [this message]
2017-04-05 1:05 ` Simon Glass
2017-03-23 23:41 ` [U-Boot] [PATCH 3/3] rockchip: rk3188: add README.rockchip paragraph describing sd boot Heiko Stuebner
2017-03-24 2:40 ` Kever Yang
2017-03-26 2:40 ` Simon Glass
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=1602950.dsGQW7ubfg@phil \
--to=heiko@sntech.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox