This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Non-working arm-unknown-linux-gnueabi toolchain (gcc-4.1.2, glibc-2.5)

From: Lennert Buytenhek <buytenh at wantstofly dot org>
To: Arvid Brodin <Arvid dot Brodin at enea dot com>
Cc: crossgcc at sourceware dot org
Date: Tue, 30 Oct 2007 15:02:46 +0100
Subject: Re: Non-working arm-unknown-linux-gnueabi toolchain (gcc-4.1.2, glibc-2.5)
References: <DC6F86A94046A64094043D44A3A708F701180863@sestoex02.enea.se> <20071030113842.GA584@xi.wantstofly.org> <DC6F86A94046A64094043D44A3A708F7011809BC@sestoex02.enea.se>

On Tue, Oct 30, 2007 at 02:15:52PM +0100, Arvid Brodin wrote:

> That did the trick! Wonderful!
> 
> Should I report this as a bug to the arm gcc ports project? (And in that
> case, would that project be the same as the "GCC ARM Improvement
> Project" on http://www.inf.u-szeged.hu/gcc-arm/index.php?)

gcc 4.1 EABI generates ARMv5 code by default.  This choice was
probably made for a good reason, so I wouldn't call this a bug per
se, but I guess it can't hurt to ask on their mailing list what
the reason is (I don't know the reason.)

--
For unsubscribe information see http://sourceware.org/lists.html#faq

Follow-Ups:
- Re: Non-working arm-unknown-linux-gnueabi toolchain (gcc-4.1.2, glibc-2.5)
  - From: Khem Raj

References:
- Non-working arm-unknown-linux-gnueabi toolchain (gcc-4.1.2, glibc-2.5)
  - From: Arvid Brodin
- Re: Non-working arm-unknown-linux-gnueabi toolchain (gcc-4.1.2, glibc-2.5)
  - From: Lennert Buytenhek
- RE: Non-working arm-unknown-linux-gnueabi toolchain (gcc-4.1.2, glibc-2.5)
  - From: Arvid Brodin

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]