From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] toolchain: add link-time-optimization support
Date: Sat, 07 Mar 2015 17:35:17 +0100 [thread overview]
Message-ID: <54FB28C5.5040107@mind.be> (raw)
In-Reply-To: <20150307172438.73f5a634@free-electrons.com>
On 07/03/15 17:24, Thomas Petazzoni wrote:
> Dear Arnout Vandecappelle,
>
> On Sat, 07 Mar 2015 17:14:29 +0100, Arnout Vandecappelle wrote:
>
>> Given that this new option (probably) changes how some packages are built, I
>> think there should be a few autobuilder configs that enable it. Any volunteers
>> to take care of that?
>
> No: the commit only allows to enable LTO support in the compiler. It
> does not start building packages with -flto, unless of course some
> packages automatically detect the availability of the LTO feature in
> the compiler and make use of it.
That's precisely what I mean. As far as I know, there isn't a single package
where we pass something like --disable-lto. Now, I'm not sure if there is any
package at all that will automatically turn on lto, but if there are then I
think we should build it.
However, I just realized that we are already building with external sourcery
and linaro toolchains that support lto. So we already have the tests that I wanted.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2015-03-07 16:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-07 14:01 [Buildroot] [git commit] toolchain: add link-time-optimization support Thomas Petazzoni
2015-03-07 16:14 ` Arnout Vandecappelle
2015-03-07 16:24 ` Thomas Petazzoni
2015-03-07 16:35 ` Arnout Vandecappelle [this message]
2015-03-07 16:43 ` Thomas Petazzoni
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=54FB28C5.5040107@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/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.