From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23055 invoked by alias); 27 Jan 2009 11:35:02 -0000 Received: (qmail 23006 invoked by uid 22791); 27 Jan 2009 11:35:01 -0000 X-SWARE-Spam-Status: No, hits=-0.8 required=5.0 tests=AWL,BAYES_20,J_CHICKENPOX_32,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 11:34:57 +0000 Received: from localhost (hagrid.ecoscentric.com [127.0.0.1]) by mail.ecoscentric.com (Postfix) with ESMTP id D8FB760B8004; Tue, 27 Jan 2009 11:34:54 +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 Jt1mO8uUemSz; Tue, 27 Jan 2009 11:34:53 +0000 (GMT) Date: Tue, 27 Jan 2009 11:35:00 -0000 Message-Id: From: Bart Veer To: John Dallaway CC: jifl@eCosCentric.com, ecos-maintainers@sourceware.org In-reply-to: <497EED0F.7070501@dallaway.org.uk> (message from John Dallaway on Tue, 27 Jan 2009 11:16:31 +0000) Subject: Re: update ARM platform HALs References: <497ED20D.3040709@dallaway.org.uk> <497EE13B.9020503@eCosCentric.com> <497EED0F.7070501@dallaway.org.uk> 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/msg00027.txt.bz2 >>>>> "Jifl" == Jonathan Larmour writes: Jifl> Actually there is one exception that should probably not be Jifl> arm-eabi which is the AEB target, which is arm7di and so Jifl> can't work with the new tools. Sorry I should have mentioned Jifl> that yesterday Bart. Maybe it's worth putting that one back, Jifl> but it may not be worth even that effort since no-one will Jifl> be using it... I think it hasn't been sold for going on 10 Jifl> years now. I'll revert the AEB to use arm-elf-gcc. >>>>> "John" == John Dallaway writes: John> IIRC, Bart observed a SIGTRAP in libgcc (udivsi3?) when John> running up eCos built with arm-eabi-gcc 4.3.2 on the ipaq John> target. So perhaps users would be better off sticking with John> arm-elf-gcc 3.2.1 for StrongARM? I'm not proposing that we John> spend any further time investigating the problem, just John> seeking clarification as to what we should recommend to John> users. That was back in October, the toolchain has been respun several times since then. This is something to look at once the checkins are complete and we have moved on to testing. Also note that there are several ARM targets which completely fail to build at the moment because of bitrot. And no doubt some number of non-ARM targets will fail to build. Again, this should be looked at after the checkins. Bart -- Bart Veer eCos Configuration Architect eCosCentric Limited The eCos experts http://www.ecoscentric.com/ Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571 Registered in England and Wales: Reg No 4422071.