From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11731 invoked by alias); 18 Jun 2012 21:07:39 -0000 Received: (qmail 11722 invoked by uid 22791); 18 Jun 2012 21:07:38 -0000 X-SWARE-Spam-Status: No, hits=-5.2 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org Received: from mail-lb0-f169.google.com (HELO mail-lb0-f169.google.com) (209.85.217.169) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 18 Jun 2012 21:07:23 +0000 Received: by lbjn8 with SMTP id n8so5821198lbj.0 for ; Mon, 18 Jun 2012 14:07:21 -0700 (PDT) Received: by 10.112.10.198 with SMTP id k6mr7083049lbb.83.1340053641514; Mon, 18 Jun 2012 14:07:21 -0700 (PDT) Received: from localhost.localdomain (host-2-96-99-49.as13285.net. [2.96.99.49]) by mx.google.com with ESMTPS id n7sm12237548lbk.10.2012.06.18.14.07.18 (version=SSLv3 cipher=OTHER); Mon, 18 Jun 2012 14:07:19 -0700 (PDT) Message-ID: <4FDF9888.1050405@googlemail.com> Date: Mon, 18 Jun 2012 21:07:00 -0000 From: David Fernandez User-Agent: Mozilla/5.0 (X11; Linux i686; rv:12.0) Gecko/20120430 Thunderbird/12.0.1 MIME-Version: 1.0 To: crossgcc@sourceware.org Subject: crt0.o from newlib has ARM32-only routines when building gcc for arm-eabi Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact crossgcc-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: crossgcc-owner@sourceware.org X-SW-Source: 2012-06/txt/msg00025.txt.bz2 Hi there, I've been building a arm-eabi toolchain recently, using binutils-2.22, gcc-4.7.1 and newlib-1.20.0 (I think). The problem is that when I build for cortex-m3 (-march=armv7-m -mcpu=cortex-m3 -mthumb), I get the routine _CRTStartup assembled as ARM32 (definitely not thumb or thumb-2). The file crt0.o seems generated during gcc build. Is that expected? As crt0.S in newlib has #ifdefs to choose the right thumb-2, thumb or ARM specific assembler depending on the predefined macros. The only thing I can think of is that it might be forced by the gcc build system, perhaps because linux does not support thumb-only platforms (?)... It might be a very silly thing, but if anybody could tell what is the problem, it would be great. Cheers David Fernandez -- For unsubscribe information see http://sourceware.org/lists.html#faq