On Friday 02 February 2001 11:44 am, Richard Earnshaw wrote:
> > Here's what I think needs doing:
> >
> > * (gcc) Support for mode-independent code (checking mode when we need to
> >   generate PC from R15).
>
> Not a major job.  Keep badgering me :-)

Grin, weekly cron job time ;)

> > * (gcc) Combined config/arm/netbsd-elf.h (mostly a copy of netbsd26.h)
> > * (gas) Support for ARM ELF PIC relocations (didn't work last time I
> >   checked)
>
> Probably requires binutils 2.10.x
>
> > * (ld.elf_so) Support for ARM ELF
> > * (ld) More sensible ARM ELF linker script (e.g. with separate text and
> >   data segments)
>
> Again, this can probably be lifted largely from binutils 2.10 linker.

Perhaps we should wait for it to get into -current (as todd said he's working 
on it)

> > > A while back you mentioned updating the ABI to something newer, which
> > > can do thumb, arm26 and arm32 (or is that a bit like the holy grail of
> > > arm processors :), do you have on docs on this or pointers to docs? 
> > > Would the ARM linux abi work?
> >
> > ARM Linux has different compiler configurations for ARMv2 and ARMv3, so
> > it's probably not the best of things to imitate.  I don't claim to
> > understand Thumb interworking.
>
> It would be cool to support ARM linux binaries with the appropriate shared
> libs and emulations.  With some work it might even be possible to make
> ARMv2 binaries run on most machines.  ARMv3 binaries might or might not be
> runnable on the old acorn machines, but you never know, it largely depends
> on whether they have to be loaded at impossible addresses.

Hmmm, I've just thought, will the .[sS] files in lib will need updating for 
the new ABI?  I'm just trying to get a grasp on the amount of work needed.  
(noting that I'm not that hot on how gcc etc works)

Chris