From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10538 invoked by alias); 27 Jan 2009 12:10:41 -0000 Received: (qmail 10516 invoked by uid 22791); 27 Jan 2009 12:10:40 -0000 X-SWARE-Spam-Status: No, hits=-0.3 required=5.0 tests=AWL,BAYES_50,J_CHICKENPOX_34,J_CHICKENPOX_41,SPF_PASS X-Spam-Check-By: sourceware.org Received: from hagrid.ecoscentric.com (HELO mail.ecoscentric.com) (212.13.207.197) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 27 Jan 2009 12:10:28 +0000 Received: from localhost (hagrid.ecoscentric.com [127.0.0.1]) by mail.ecoscentric.com (Postfix) with ESMTP id 62ECA60B8004; Tue, 27 Jan 2009 12:10:26 +0000 (GMT) Received: from mail.ecoscentric.com ([127.0.0.1]) by localhost (hagrid.ecoscentric.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gHS2a6BrNTiP; Tue, 27 Jan 2009 12:10:23 +0000 (GMT) Message-ID: <497EF9B6.2030009@eCosCentric.com> Date: Tue, 27 Jan 2009 12:10:00 -0000 From: Jonathan Larmour User-Agent: Mozilla Thunderbird 1.0.8-1.1.fc3.4.legacy (X11/20060515) MIME-Version: 1.0 To: John Dallaway 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> In-Reply-To: <497EED0F.7070501@dallaway.org.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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/msg00028.txt.bz2 John Dallaway wrote: > 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. 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. Of course, I don't expect anyone to be using strongarm in new designs as they've been discontinued. Jifl -- eCosCentric Limited http://www.eCosCentric.com/ The eCos experts Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571 Registered in England and Wales: Reg No 4422071. ------["The best things in life aren't things."]------ Opinions==mine