From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23244 invoked by alias); 22 Nov 2011 22:14:02 -0000 Received: (qmail 23234 invoked by uid 22791); 22 Nov 2011 22:14:02 -0000 X-SWARE-Spam-Status: No, hits=-1.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE X-Spam-Check-By: sourceware.org Received: from smtp04.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.126) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 22 Nov 2011 22:13:48 +0000 Received: from treguer.localnet ([90.32.33.236]) by mwinf5d27 with ME id 0NDm1i00A55gilm03NDmPQ; Tue, 22 Nov 2011 23:13:46 +0100 From: "Yann E. MORIN" To: crossgcc@sourceware.org Subject: Re: [PATCH] libc/newlib: Add optspace config for newlib Date: Tue, 22 Nov 2011 22:14:00 -0000 User-Agent: KMail/1.13.5 (Linux/3.1.1-treguer; KDE/4.4.5; x86_64; ; ) Cc: Michael Hope , Zhenqiang Chen References: <4ECB872F.8010101@linaro.org> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201111222313.46306.yann.morin.1998@anciens.enib.fr> Mailing-List: contact crossgcc-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: crossgcc-owner@sourceware.org X-SW-Source: 2011-11/txt/msg00138.txt.bz2 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