From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5289 invoked by alias); 27 Jan 2009 12:41:42 -0000 Received: (qmail 5281 invoked by uid 22791); 27 Jan 2009 12:41:42 -0000 X-SWARE-Spam-Status: No, hits=-1.6 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_34,J_CHICKENPOX_41 X-Spam-Check-By: sourceware.org Received: from mtaout01-winn.ispmail.ntl.com (HELO mtaout01-winn.ispmail.ntl.com) (81.103.221.47) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 27 Jan 2009 12:41:36 +0000 Received: from aamtaout02-winn.ispmail.ntl.com ([81.103.221.35]) by mtaout01-winn.ispmail.ntl.com (InterMail vM.7.08.04.00 201-2186-134-20080326) with ESMTP id <20090127124133.UFKV2989.mtaout01-winn.ispmail.ntl.com@aamtaout02-winn.ispmail.ntl.com>; Tue, 27 Jan 2009 12:41: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 <20090127124128.ICGI21638.aamtaout02-winn.ispmail.ntl.com@cog.dallaway.org.uk>; Tue, 27 Jan 2009 12:41:28 +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 n0RCfPKm014454; Tue, 27 Jan 2009 12:41:26 GMT Message-ID: <497F00F5.6070306@dallaway.org.uk> Date: Tue, 27 Jan 2009 12:41: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> <497EED0F.7070501@dallaway.org.uk> <497EF9B6.2030009@eCosCentric.com> In-Reply-To: <497EF9B6.2030009@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/msg00029.txt.bz2 Jifl Jonathan Larmour wrote: > John Dallaway wrote: > >> 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. > > Well, I've had a closer look, and indeed the prebuilt tools won't just > work after all, because, even if thumb interworking is disabled, gcc > uses ARMv4t insns like 'bx', which aren't available on strongarm's ARMv4. > > If people want to use strongarm, they can indeed either use the older > tools, or rebuild the current tools with strongarm multilibs added. OK. Thanks for the clarification. > Of course, I don't expect anyone to be using strongarm in new designs as > they've been discontinued. Yes, I appreciate that this is unlikely to affect many users. The set of multi-libs in the pre-built arm-eabi tools seems perfectly reasonable for eCos in 2009. John Dallaway