[fpc-pascal] Arm EABI vs OABI [was:DateToStr in arm does not work!]

Marc Santhoff M.Santhoff at t-online.de
Sun Jul 8 20:03:01 CEST 2007

Am Sonntag, den 08.07.2007, 19:31 +0200 schrieb Luca Olivetti:
> En/na Jonas Maebe ha escrit:
> > 
> > On 08 Jul 2007, at 18:06, Luca Olivetti wrote:
> > 
> >>> I don't think anyone has ever tried to use the libc-based rtl with 
> >>> linux/arm.
> >>
> >> And without using libc, what kind of syscalls do fpc generate OABI or 
> >> EABI? (or, again, is there no difference between the two?)
> > 
> > I have no idea. You could try comparing /usr/include/asm/unistd.h on an 
> > OABI and EABI system for a start, although that will tell you nothing 
> > about which parameters have to be passed and in what way (only the 
> > syscall numbers themselves).
> supposedly (I'm not really into system level programming) oabi syscalls 
> start at 0x900000, while eabi ones start at 0, so, by looking at 
> rtl/linux/arm/sysnr.inc it seems that fpc should be generating oabi 
> calls, so my problems with arm are coming from somewhere else.

Can't you try to write a simple program using the functions in question
and compile with "fpc -al"?

That way the assembler source should show some useful information about
the system calls in use.


More information about the fpc-pascal mailing list