Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Config.in: add -Ofast option
Date: Sun, 25 Mar 2018 22:40:31 +0200	[thread overview]
Message-ID: <20180325224031.55cfb6a8@windsurf> (raw)
In-Reply-To: <20180325082434.GF2620@scaer>

Hello,

On Sun, 25 Mar 2018 10:24:34 +0200, Yann E. MORIN wrote:

> > +config BR2_OPTIMIZE_FAST
> > +	bool "optimize for fast"  
> 
> -Ofast was introduced in gcc-4.6, so you need a dependency:
>     depends on BR2_TOOLCHAIN_GCC_AT_LEAST_4_6

The "odd" thing being that menuconfig is organized as follows:

 Target options --->
 Build options --->
 Toolchain --->

The optimization level is selected in "Build options" and the compiler
version is basically decided in "Toolchain".

So if you select -Ofast in Build options, and then go in Toolchain
chose a < 4.6 compiler, your -Ofast selection would disappear.

But there's no good way around this, and using gcc < 4.6 is anyway very
rare these days, so I also agree that the "depends on" you suggest is
what makes the most sense.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-03-25 20:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-22 16:26 [Buildroot] [PATCH] Config.in: add -Ofast option Joshua Henderson
2018-03-25  8:24 ` Yann E. MORIN
2018-03-25 20:40   ` Thomas Petazzoni [this message]
2018-03-26 16:12     ` Yann E. MORIN

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=20180325224031.55cfb6a8@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox