From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20825 invoked by alias); 20 Jan 2012 14:42:00 -0000 Received: (qmail 20817 invoked by uid 22791); 20 Jan 2012 14:41:59 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,RCVD_IN_DNSWL_NONE X-Spam-Check-By: sourceware.org Received: from elasmtp-junco.atl.sa.earthlink.net (HELO elasmtp-junco.atl.sa.earthlink.net) (209.86.89.63) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 20 Jan 2012 14:41:46 +0000 Received: from [97.23.191.52] (helo=[192.168.0.5]) by elasmtp-junco.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1RoFen-0003MT-GS; Fri, 20 Jan 2012 09:41:35 -0500 Message-ID: <4F197D15.2020700@mindspring.com> Date: Fri, 20 Jan 2012 14:42:00 -0000 From: Frank Pagliughi User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.24) Gecko/20111108 Fedora/3.1.16-1.fc14 Lightning/1.0b2 Thunderbird/3.1.16 MIME-Version: 1.0 To: Ilija Kocho CC: ecos-devel@ecos.sourceware.org Subject: Re: Gnutools: consideration for upgrade to GCC 4.6 References: <4F106345.4080902@siva.com.mk> <4F15412B.9040601@r-finger.com> <4F159D3C.1060108@meduna.org> <4F15A57E.3090608@siva.com.mk> In-Reply-To: <4F15A57E.3090608@siva.com.mk> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-ELNK-Trace: 4d82f965df0f6dd9e3f977c6d1ea408f0a9da525759e2654dc9fc458f172094c8eeaa28e5b7200a430febb85a5f48815350badd9bab72f9c350badd9bab72f9c X-IsSubscribed: yes Mailing-List: contact ecos-devel-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: ecos-devel-owner@ecos.sourceware.org X-SW-Source: 2012-01/txt/msg00031.txt.bz2 On 01/17/2012 11:44 AM, Ilija Kocho wrote: > On 17.01.2012 17:09, Stanislav Meduna wrote: >> On 17.01.2012 10:36, Tomas Frydrych wrote: >> >>> Some of the more recent gccs were not producing usable binaries on some >>> platforms (including arm) with the -Os option. I do not know if this is >>> the case with 4.6.2, and I don't think ecos uses -Os by default, but it >>> is probably worth checking whether this works (and at least documenting >>> somewhere if it does not). >> Do you happen to have more details on this - versions, flags used, >> example to reproduce...? >> >> http://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html says >> >> -Os enables all -O2 optimizations that do not typically increase >> code size. It also performs further optimizations designed >> to reduce code size. >> >> it would be good to know whether the problems come from -O2 (which >> would be a major problem) or from these further optimizations. > > I am compiling with default eCos options (that include -O2). Haven't > noticed a problems so far. > > > Ilija > It would be pretty cool if we made a script that downloaded and built the eCos GNU tools for the current "official" version. Add the script to the source control. That way we'd all have a good starting point when upgrading personal tool chains. And, while we're at it, update the ancient directions on the web site on how to build a tool chain: http://ecos.sourceware.org/build-toolchain.html Frank