[fpc-devel] arm eabi test suite
jonas.maebe at elis.ugent.be
Sat Aug 22 09:02:32 CEST 2009
On 22 Aug 2009, at 00:41, Henry Vermaak wrote:
> I've managed to run a native testsuite on my nslu2, I can email the
> tarball if anyone is interested (I think the mailing list will reject
Is it different from the tarball you attached to http://bugs.freepascal.org/view.php?id=14386
? I already imported that one into the testsuite database: http://www.freepascal.org/testsuite/cgi-bin/testsuite.cgi?action=1&run1id=42245&run2id=&noskipped=1&failedonly=1
> There are a couple of backtraces also in the longlog, which I attach,
> too. Not sure if it is helpful.
> I spotted some asm in ossysc.inc that will not work on eabi:
> swi syscall_nr_sigreturn (same for rt_sigreturn)
> For eabi this should probably be:
> mov r7,syscall_nr_sigreturn
> swi #0x0
> But should r7 saved before and restored afterwards?
There is no "afterwards" for a sigreturn system call, as it restores
the context that was saved when the signal was triggered (so code
coming after the swi is never executed, except possibly in case of an
error that didn't crash the program).
> I don't know how to test this code.
You normally never need to explicitly use this system call. The kernel
usually puts a stub somewhere in memory containing this system call
and makes the return address of signal handlers point to that stub.
More information about the fpc-devel