Subject: Re: ARM ELF TODO list
To: Chris Gilbert <firstname.lastname@example.org>
From: Jason R Thorpe <email@example.com>
Date: 11/15/2001 15:47:16
On Mon, Oct 29, 2001 at 09:03:49AM +0000, Chris Gilbert wrote:
> > Needed before the changeover:
> > * (gcc) Ensure 8-byte stack alignment on function entry [rearnsha]
Any guesses on how hard this will be to implement in the compiler?
> > * (gcc) packed enums (should be trivial to implement in the compiler, but
> > I've heard rumours it might break openssh)
What does the ARM ELF ABI document actually say about this? If it's
sufficiently vague (which I've heard that it is), why not just ignore
the packed enum issue (i.e. stick w/ fixed-size enums like we have now)?
> > * (asm sources) Ensure these preserve 8-byte stack alignment if not leaf
> > functions [chris]
I see Chris committed this. What about the kernel... do we have to care
about the kernel, in this case?
> Actually has anyone got an ELF kernel for a CATS. I'd like to try one out
> and see if it actually boots, or if we need to do the same thing that's
> needed on dnard, and ELF->a.out convertor (I think that's what's planned)
I can build you an ELF kernel, but I suspect the CATS firmware wants to
boot a.out. Can the CATS firmware boot plain binary? What about S-Records?
Are there firmware I/O callbacks so that you could write a bootloader?
FWIW, I did make a little progress with an ofwboot for the Shark, so
that I can load ELF kernels. But I seem to be bumping into OpenFirmare
bugs (!??!!) ... the first OFW call made by the kernel results in a
Data Abort in OFW code! I need to spend some more time on it.
-- Jason R. Thorpe <firstname.lastname@example.org>