Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Arnout Vandecappelle (Essensium/Mind)" <arnout@mind.be>
Cc: "Peter Kümmel" <syntheticpp@gmx.net>,
	"Douglas RAILLARD" <public.douglas.raillard@gmail.com>,
	"Dario Binacchi" <dariobin@libero.it>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/5] Config.in: add new option BR2_ENABLE_LTO to globally enable LTO
Date: Tue, 26 Jul 2022 21:57:34 +0200	[thread overview]
Message-ID: <20220726215734.253e9455@windsurf> (raw)
In-Reply-To: <20220725152229.3370033-1-arnout@mind.be>

On Mon, 25 Jul 2022 17:22:25 +0200
"Arnout Vandecappelle (Essensium/Mind)" <arnout@mind.be> wrote:

> Some packages have a configure option to enable LTO. Add a global option
> to enable/disable this in packages.
> 
> Note that we could instead (or in addition) pass -flto directly to the
> compiler in the toolchain wrapper, but that has a *much* bigger impact,
> so for the time being let's not do that.
> 
> No toolchain dependency is added for this, because all toolchains now
> support LTO.
> - LTO support was merged in GCC years before 4.6 (our minimal version)
>   was released.
> - Our oldest external toolchain, Sourcery ARM 2014.05, has LTO support.
> - For our internal toolchains, it is supposedly regulated by
>   BR2_GCC_ENABLE_LTO. However, that option only *enables* it - it
>   doesn't disable LTO support when it's not provided. Since LTO support
>   defaults to enabled for a long time already in GCC, in practice all
>   Buildroot-generated toolchains do support LTO.
> 
> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> ---
>  Config.in | 19 +++++++++++++++++++
>  1 file changed, 19 insertions(+)

Series applied, thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2022-07-26 19:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-25 15:22 [Buildroot] [PATCH 1/5] Config.in: add new option BR2_ENABLE_LTO to globally enable LTO Arnout Vandecappelle (Essensium/Mind)
2022-07-25 15:22 ` [Buildroot] [PATCH 2/5] package/*: use BR2_ENABLE_LTO to enable LTO instead of BR2_GCC_ENABLE_LTO Arnout Vandecappelle (Essensium/Mind)
2022-07-25 15:22 ` [Buildroot] [PATCH 3/5] configs/*: " Arnout Vandecappelle (Essensium/Mind)
2022-07-25 15:22 ` [Buildroot] [PATCH 4/5] package/binutils: remove BR2_BINUTILS_ENABLE_LTO Arnout Vandecappelle (Essensium/Mind)
2022-07-25 15:22 ` [Buildroot] [PATCH 5/5] package/gcc: remove BR2_GCC_ENABLE_LTO Arnout Vandecappelle (Essensium/Mind)
2022-07-26 19:57 ` Thomas Petazzoni via buildroot [this message]

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=20220726215734.253e9455@windsurf \
    --to=buildroot@buildroot.org \
    --cc=arnout@mind.be \
    --cc=dariobin@libero.it \
    --cc=public.douglas.raillard@gmail.com \
    --cc=syntheticpp@gmx.net \
    --cc=thomas.petazzoni@bootlin.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