From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12491 invoked by alias); 27 Jan 2009 11:16:56 -0000 Received: (qmail 12482 invoked by uid 22791); 27 Jan 2009 11:16:55 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_34 X-Spam-Check-By: sourceware.org Received: from mtaout02-winn.ispmail.ntl.com (HELO mtaout02-winn.ispmail.ntl.com) (81.103.221.48) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 27 Jan 2009 11:16:40 +0000 Received: from aamtaout02-winn.ispmail.ntl.com ([81.103.221.35]) by mtaout02-winn.ispmail.ntl.com (InterMail vM.7.08.04.00 201-2186-134-20080326) with ESMTP id <20090127111633.IYAO4080.mtaout02-winn.ispmail.ntl.com@aamtaout02-winn.ispmail.ntl.com>; Tue, 27 Jan 2009 11:16:33 +0000 Received: from cog.dallaway.org.uk ([213.106.81.244]) by aamtaout02-winn.ispmail.ntl.com (InterMail vG.2.02.00.01 201-2161-120-102-20060912) with ESMTP id <20090127111633.GRWH21638.aamtaout02-winn.ispmail.ntl.com@cog.dallaway.org.uk>; Tue, 27 Jan 2009 11:16:33 +0000 Received: from cog.dallaway.org.uk (cog.dallaway.org.uk [127.0.0.1]) by cog.dallaway.org.uk (8.13.8/8.13.8) with ESMTP id n0RBGVSp011744; Tue, 27 Jan 2009 11:16:31 GMT Message-ID: <497EED0F.7070501@dallaway.org.uk> Date: Tue, 27 Jan 2009 11:16:00 -0000 From: John Dallaway User-Agent: Thunderbird 2.0.0.19 (X11/20090107) MIME-Version: 1.0 To: Jonathan Larmour CC: ecos-maintainers@sourceware.org Subject: Re: update ARM platform HALs References: <497ED20D.3040709@dallaway.org.uk> <497EE13B.9020503@eCosCentric.com> In-Reply-To: <497EE13B.9020503@eCosCentric.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact ecos-maintainers-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: ecos-maintainers-owner@ecos.sourceware.org X-SW-Source: 2009-01/txt/msg00026.txt.bz2 Hi Jifl Jonathan Larmour wrote: > John Dallaway wrote: > >> The eCosCentric arm-eabi pre-built toolchains do not include StrongARM >> multi-libs. AFAIK, users who want to build eCos for these targets will >> therefore need to either build their own arm-eabi-gcc or revert to >> CYGBLD_GLOBAL_COMMAND_PREFIX == "arm-elf" and use the older arm-elf-gcc >> 3.2.1. Can you please let me know what the intention is here so I can >> mention this in the eCos 3.0 release notes? > > This was discussed before IRL, and I believe until I hear to the > contrary that strongarm should probably still work. It just won't be > perfectly optimal as it will fall back to the arm7tdmi multilib (the > default); but now actually looking at GCC sources, I think it may have > only a virtually perceptible effect even then. IIRC, Bart observed a SIGTRAP in libgcc (udivsi3?) when running up eCos built with arm-eabi-gcc 4.3.2 on the ipaq target. So perhaps users would be better off sticking with arm-elf-gcc 3.2.1 for StrongARM? I'm not proposing that we spend any further time investigating the problem, just seeking clarification as to what we should recommend to users. John Dallaway