> "Paul" == Paul Brook writes:
Paul> IMHO building lots of multilibs by default significantly increases
Paul> toolchain size and build time for little actual benefit. ARM CPUs
Paul> are generally backwards compatible and we only have one important
Paul> ABI variant, so very few multilibs are
> Meh. Badly written code on antique hardware.
> I realise this sounds harsh, but in all seriousness if you take a bit of care
Yes, I think it does sound harsh, considering that, I believe, at least as
many chips are sold with ARM7TDMI core as the nice fat chips with MMU,
caches, 64 and 128 bit bu
On Thu, Oct 1, 2009 at 20:22, Paul Brook wrote:
>
> > > Almost certainly not. As far as I'm concerned arm-elf is obsolete, and in
> > > maintenance only mode. You should be using arm-eabi.
Is it now possible to build a 100% arm-eabi functional toolchain
(including i.e. newlib) in multilib mode st
> > Almost certainly not. As far as I'm concerned arm-elf is obsolete, and in
> > maintenance only mode. You should be using arm-eabi.
>
> I'm possibly (probably?) wrong, but as far as I know, it forces alignment
> of 64-bit datum (namely, doubles and long longs) to 8 byte boundaries,
> which does
> Since this will be arm-rtems multilib's when submitted,
> which variants and matches need to be added so we have
> the right libraries for all CPU model arguments. ld is
> complaining at least about libc.a mismatches for these variations.
>
> does not use Maverick instructions, whereas a.out
On Thu, 1 Oct 2009, Paul Brook wrote:
> > Do we want to enable more multilibs in arm-elf?
>
> Almost certainly not. As far as I'm concerned arm-elf is obsolete, and in
> maintenance only mode. You should be using arm-eabi.
I'm possibly (probably?) wrong, but as far as I know, it forces alignmen
Paul Brook wrote:
Do we want to enable more multilibs in arm-elf?
Almost certainly not. As far as I'm concerned arm-elf is obsolete, and in
maintenance only mode. You should be using arm-eabi.
IMHO building lots of multilibs by default significantly increases toolchain
size and build t
> Do we want to enable more multilibs in arm-elf?
Almost certainly not. As far as I'm concerned arm-elf is obsolete, and in
maintenance only mode. You should be using arm-eabi.
IMHO building lots of multilibs by default significantly increases toolchain
size and build time for little actual ben
