From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: crossgcc@sourceware.org
Cc: Johannes Stezenbach <js@sig21.net>
Subject: Re: ct-ng seems to disable all optimization by default
Date: Fri, 24 Feb 2012 22:02:00 -0000 [thread overview]
Message-ID: <201202242302.16695.yann.morin.1998@free.fr> (raw)
In-Reply-To: <20120216144551.GA2416@sig21.net>
Johannes, All,
On Thursday 16 February 2012 15:45:52 Johannes Stezenbach wrote:
> I've been looking through the build.log and found that
> most parts of the toolchain are build without -O2 or similar.
> This seems to be caused by ct-ng build scripts passing CFLAGS
> unconditionally to ./configure, which causes it to _replace_
> any default CFLAGS with the given ones -- in my
> case (with CT_USE_PIPES=y) " -pipe".
>
> I guess the easy solution is CT_EXTRA_FLAGS_FOR_HOST="-O2"
> and CT_TARGET_CFLAGS="-Os" (or similar).
>
> To me this behaviour is unexpected because CT_EXTRA_FLAGS_FOR_HOST
> help talks about "additional" CFLAGS.
Yes, what is provided in the menuconfig should be added in a way that it
overrides the computed values. In this case, the additional CFLAGS should
be added after the internally-computed ones, yes.
I'll look at it this WE (although that's gonna be a short one, anti-ACTA
demonstration sat. PM).
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. |
'------------------------------^-------^------------------^--------------------'
--
For unsubscribe information see http://sourceware.org/lists.html#faq
prev parent reply other threads:[~2012-02-24 22:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 14:46 Johannes Stezenbach
2012-02-24 22:02 ` 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=201202242302.16695.yann.morin.1998@free.fr \
--to=yann.morin.1998@free.fr \
--cc=crossgcc@sourceware.org \
--cc=js@sig21.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).