public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
To: crossgcc@sourceware.org
Cc: Michael Hope <michael.hope@linaro.org>,
	Zhenqiang Chen <zhenqiang.chen@linaro.org>
Subject: Re: [PATCH] libc/newlib: Add optspace config for newlib
Date: Tue, 22 Nov 2011 22:14:00 -0000	[thread overview]
Message-ID: <201111222313.46306.yann.morin.1998@anciens.enib.fr> (raw)
In-Reply-To: <CANLjY-mue0otPrwGrHvtP3czZzrucosVjChqDhgxGViP5K60og@mail.gmail.com>

Michael, Zhenqiang, All,

On Tuesday 22 November 2011 21:22:50 Michael Hope wrote:
> A question for the list: there's already a 'Optimise the GCC runtime
> libraries for space' option.  Should it be promoted to something like
> CT_ENABLE_TARGET_OPTSPACE and apply to all target libraries?

Sounds reasonable to me. I think the proper place would probably be in
the "Target options" sub-menu, in "Target optimisations", just before
the inclusion of "arch.in.2".

> How you
> you handle backwards compatibility of config files?

That's deliberately not handled.

So, an option rename is not caught (if that's what you were thinking).
But I don't think this should be a show-stopper.

> I have a similar problem with CC_STATIC_LIBSTDCXX.  GOLD is written in
> C++ and really needs to have libstdc++ statically linked into it.  I'm
> thinking of sending a patch that promotes CT_CC_STATIC_LIBSTDCXX to
> CT_STATIC_LIBSTDCXX and uses it everywhere.

Sounds reasonable to me, too; just below (STATIC_TOOLCHAIN) "Build Static
Toolchain". Beware, STATIC_TOOLCHAIN is also defined in config/cc/gcc.in.2.

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

  reply	other threads:[~2011-11-22 22:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-22 11:28 Zhenqiang Chen
2011-11-22 20:23 ` Michael Hope
2011-11-22 22:14   ` Yann E. MORIN [this message]
2011-11-22 23:05 ` 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=201111222313.46306.yann.morin.1998@anciens.enib.fr \
    --to=yann.morin.1998@anciens.enib.fr \
    --cc=crossgcc@sourceware.org \
    --cc=michael.hope@linaro.org \
    --cc=zhenqiang.chen@linaro.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).