From: Mark Hatle <mark.hatle@windriver.com>
To: Trevor Woerner <twoerner@gmail.com>,
OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: noticeably longer build (link?) times with binutils 2.26
Date: Mon, 8 Feb 2016 18:25:14 -0600 [thread overview]
Message-ID: <56B931EA.6060107@windriver.com> (raw)
In-Reply-To: <56B922B3.9070604@gmail.com>
Which arch/tune are you targeting? I know that on a few processors 2.26 has
added "link time optimization" (i.e. our processor is broken and we're working
around problems in the linker.)
It's possible you hit one of those cases, or it may simply be that much slower
for some reason. But worse then double the time is really terrible.
On 2/8/16 5:20 PM, Trevor Woerner wrote:
> This is more of a "FYI", but I've noticed that the build time of my
> chromium recipe has gone from ~45 minutes to ~2h15m when the only thing
> that changes is to move openembedded-core from the commit just before
> upgrading binutils to version 2.26 ([fd75637] native.bbclass: Set
> CXXFLAGS from BUILD_CXXFLAGS not BUILD_CFLAGS) to the one immediately
> after ([86ade2c] binutils: Upgrade to 2.26).
>
> Oddly enough I don't see this same behaviour when building, for example,
> core-image-minimal, so I have no idea what makes chromium so special
> and, therefore, whether other recipes might be similarly affected.
>
> Also, it seems as though a lot of the added time is coming from the
> linking stage, but I don't have (or know how to get) hard numbers for
> that. Is there a way to get build times for each task within one recipe?
>
> I've repeated this test 6 times (build just before binutils-2.26, build
> just after binutils-2.26) and the results are always within a couple
> minutes of each other. So I doubt this is some random occurrence.
>
next prev parent reply other threads:[~2016-02-09 0:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 23:20 noticeably longer build (link?) times with binutils 2.26 Trevor Woerner
2016-02-09 0:25 ` Mark Hatle [this message]
2016-02-09 2:56 ` Trevor Woerner
2016-02-09 10:00 ` Burton, Ross
2016-02-09 15:34 ` Trevor Woerner
2016-02-09 2:25 ` Khem Raj
2016-02-09 3:03 ` Trevor Woerner
2016-02-09 3:05 ` Khem Raj
2016-02-10 4:18 ` Trevor Woerner
2016-02-10 4:37 ` Khem Raj
2016-02-11 17:25 ` Trevor Woerner
2016-02-11 17:29 ` Khem Raj
2016-02-11 19:20 ` Martin Jansa
2016-02-11 22:14 ` Trevor Woerner
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=56B931EA.6060107@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=twoerner@gmail.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