Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot: gcc options
Date: Wed, 20 Nov 2013 08:45:23 -0300	[thread overview]
Message-ID: <528CA0D3.8040906@zacarias.com.ar> (raw)
In-Reply-To: <528B9E7C.1010804@mind.be>

On 11/19/2013 02:23 PM, Arnout Vandecappelle wrote:

>  Is there any reason why BR2_TARGET_OPTIMIZATIONS isn't used for
> building the C library?

The libc is somewhat fragile when built with some insane CFLAGS, for
instance (e)glibc is built at O2 (by Thomas P), allowing a switch to
another optimization level might be troublesome.
uClibc forces -Os in Rules.mak for BUILD_CFLAGS for example.
I'm unsure if we'd like to open pandora's box by merging them, maybe add
an option just for the libc?
Regards.

  reply	other threads:[~2013-11-20 11:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-15  9:03 [Buildroot] buildroot: gcc options Altunbas Sabri
2013-11-15  9:13 ` Thomas De Schampheleire
2013-11-15  9:38   ` Altunbas Sabri
2013-11-15  9:41     ` Thomas De Schampheleire
2013-11-15  9:57       ` Altunbas Sabri
2013-11-15 10:02         ` Thomas De Schampheleire
2013-11-15 10:05           ` Altunbas Sabri
2013-11-15 10:10             ` Thomas De Schampheleire
2013-11-15 10:25               ` Altunbas Sabri
2013-11-15 10:38                 ` Thomas De Schampheleire
2013-11-19 12:17                   ` Altunbas Sabri
2013-11-19 12:30                     ` Gustavo Zacarias
2013-11-19 17:23                       ` Arnout Vandecappelle
2013-11-20 11:45                         ` Gustavo Zacarias [this message]
2013-11-20 12:10                       ` Altunbas Sabri

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=528CA0D3.8040906@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --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