A quick review of src/runtime/arm-arch.c suggests that the only linux-specific piece is the pseudo-atomic-interrupted flag being a syscall number. The trap handlers should be fairly generic as-is, at least the ones that aren't #if 0'd out.

If you're porting to another OS, you'll need to re-evaluate the implementation of pseudo-atomic anyway, as it uses a conditional EABI Linux syscall to generate the pending-interrupt trap... Unless someone has changed that since I wrote it?

-- Alastair Bridgewater

On Tue, Jul 15, 2014 at 8:50 AM, Robert Swindells <rjs@fdy2.co.uk> wrote:

A lot of the code in src/runtime/arm-arch.c is Linux specific, do people
have a preference for what to do when porting it to a different OS ?

I think it would look cleaner if the trap handlers and the
pseudo_atomic_interrupted stuff was moved to arm-linux-os.c.

Robert Swindells

Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
Sbcl-devel mailing list