Re: M0 and M3 patches in linaro toolchains

2013-10-07 Thread Keith Packard
Matthew Gretton-Dann writes: > Can you please provide the output of: > 1. arm-none-eabi-gcc -v > 2. arm-none-eabi-gcc -print-multi-lib Yeah, I figured it out, thanks -- the patches I had to add ARM multilib support updated configure.ac but I didn't rebuild the configure script, so my attempt

Re: M0 and M3 patches in linaro toolchains

2013-10-07 Thread Ard Biesheuvel
On 7 October 2013 11:30, Matthew Gretton-Dann wrote: > On 7 October 2013 05:20, Keith Packard wrote: [...] >> 2) The thumb version of libgcc.a is not built with thumb instructions >> because GCC doesn't pass -mthumb to the assembler when it receives >> -mthumb on the command line. > >

Re: M0 and M3 patches in linaro toolchains

2013-10-07 Thread Matthew Gretton-Dann
Keith On 7 October 2013 05:20, Keith Packard wrote: > Matthias Klose writes: > >> attaching a diff, comparing the two branches at a merge point >> (r201326), 398 lines. > > Ok, thanks very much for this simple patch. First the good news -- I > applied this patch to the 4.8.1 GCC sources included

Re: M0 and M3 patches in linaro toolchains

2013-10-06 Thread Keith Packard
Matthias Klose writes: > Am 19.08.2013 17:27, schrieb Keith Packard: >> Wookey writes: >> >>> The alternative it to simply repack the existing linaro >>> cross-toolchain sources, but them we get to keep doing that for new >>> releases, and we have gratuitous extra copies of gcc sources and >>>

Re: M0 and M3 patches in linaro toolchains

2013-09-18 Thread Matthias Klose
Am 19.08.2013 17:27, schrieb Keith Packard: > Wookey writes: > >> The alternative it to simply repack the existing linaro >> cross-toolchain sources, but them we get to keep doing that for new >> releases, and we have gratuitous extra copies of gcc sources and >> corresponding differences between

RE: M0 and M3 patches in linaro toolchains

2013-08-24 Thread Keith Packard
Joey Ye writes: > I'm not sure what blocked M0. There are a few things suspicious: > * Which C library is used? The one gcc-arm-embedded works, and the only one > I know works for Cortex-M, is newlib. Other than that, good luck :-( I'm using pdclib, which is not the best solution in most ways ex

RE: M0 and M3 patches in linaro toolchains

2013-08-23 Thread Joey Ye
> -Original Message- > From: Wookey [mailto:woo...@wookware.org] > Sent: Tuesday, August 20, 2013 0:31 > To: linaro-dev@lists.linaro.org; Embedded Debian > Cc: Joey Ye > Subject: Re: M0 and M3 patches in linaro toolchains > > +++ Matthew Gretton-Dann [2013-08-19

RE: M0 and M3 patches in linaro toolchains

2013-08-22 Thread Joey Ye
> -Original Message- > From: Wookey [mailto:woo...@wookware.org] > Sent: Tuesday, August 20, 2013 0:31 > To: linaro-dev@lists.linaro.org; Embedded Debian > Cc: Joey Ye > Subject: Re: M0 and M3 patches in linaro toolchains > > +++ Matthew Gretton-Dann [2013-08-19

Re: M0 and M3 patches in linaro toolchains

2013-08-19 Thread Keith Packard
Wookey writes: > The alternative it to simply repack the existing linaro > cross-toolchain sources, but them we get to keep doing that for new > releases, and we have gratuitous extra copies of gcc sources and > corresponding differences between A* and M* toolchains/versions. I'm working on this

Re: M0 and M3 patches in linaro toolchains

2013-08-19 Thread Wookey
+++ Matthew Gretton-Dann [2013-08-19 16:58 +0100]: > On 19 August 2013 15:04, Wookey wrote: > > Debconf13 (last week) considered the matter of bare-metal > > cross-toolchains in Debian. > > The linaro embedded toolchains > > (https://launchpad.net/gcc-arm-embedded/4.7/4.7-2013-q1-update) are > >

Re: M0 and M3 patches in linaro toolchains

2013-08-19 Thread Matthew Gretton-Dann
On 19 August 2013 15:04, Wookey wrote: > Debconf13 (last week) considered the matter of bare-metal > cross-toolchains in Debian. Ideally we would have one toolchain source > package from which the existing linux native compilers, and > cross-compilers are built, including bare-metal cross-compiler

M0 and M3 patches in linaro toolchains

2013-08-19 Thread Wookey
Debconf13 (last week) considered the matter of bare-metal cross-toolchains in Debian. Ideally we would have one toolchain source package from which the existing linux native compilers, and cross-compilers are built, including bare-metal cross-compilers. There is already mechanism for adding patches