From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Config.in: add -Ofast option
Date: Mon, 26 Mar 2018 18:12:40 +0200 [thread overview]
Message-ID: <20180326161240.GB2736@scaer> (raw)
In-Reply-To: <20180325224031.55cfb6a8@windsurf>
Thomas, All,
On 2018-03-25 22:40 +0200, Thomas Petazzoni spake thusly:
> 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.
Yeah, I know. But, as you ssay:
> But there's no good way around this, and using gcc < 4.6 is anyway very
... there's no good solution around this issue, and the case for gcc
before 4.6 is rare enough that we don't care abot those poor souls
anymore... :-/
> rare these days, so I also agree that the "depends on" you suggest is
> what makes the most sense.
Was that an Acked-by or a Reviewed-by? ;-)
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2018-03-26 16:12 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
2018-03-26 16:12 ` Yann E. MORIN [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=20180326161240.GB2736@scaer \
--to=yann.morin.1998@free.fr \
--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.