public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Johannes Stezenbach <js@sig21.net>
To: crossgcc@sourceware.org
Subject: ct-ng seems to disable all optimization by default
Date: Thu, 16 Feb 2012 14:46:00 -0000	[thread overview]
Message-ID: <20120216144551.GA2416@sig21.net> (raw)

Hi,

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.


Johannes

--
For unsubscribe information see http://sourceware.org/lists.html#faq

             reply	other threads:[~2012-02-16 14:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-16 14:46 Johannes Stezenbach [this message]
2012-02-24 22:02 ` 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=20120216144551.GA2416@sig21.net \
    --to=js@sig21.net \
    --cc=crossgcc@sourceware.org \
    /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).