Getting modules ready for 64-bit RISC OS

I thought I’d documented converting C code in assembler.

I thought I’d documented

Link?

That would be helpful- I know of someone with a module who would like to get it working on newer hardware.

Does anyone fancy coming to the next fireside chat on Saturday, 12th October, to help? I’m appealing to the people in this thread and the wider community.

I think this would also make an interesting topic for a talk.

EDIT: I’ve reposted and created a new thread, “Moving software 26-bit to 32-bit”, in “Community Support” to keep this one on track.

JS wrote:

• How can I make my module 64-bit ready?
• How can I test if my module is 64-bit ready?
• Once I’ve reviewed my module, how can I declare that I think it’s 64-bit ready?

Is it possible to let us know where to find the module now? Then anyone really interested can have a look, perhaps try things, and be better prepared for the chat.

Sprow wrote (on 1st page of thread):

“On that last point, heres a bit of 32 bit compatible C

swix(OSValidateAddress, _INR(0,1) | OUT(FLAGS), start, end, &carry);

and here it is rewritten to be 64 bit compatible

swix(OSValidateAddress, _INR(0,1) | OUT(FLAGS), start, end, &carry);”

This looks useful; how does one set output registers? If it is | _OUTR(1), how do you modify the register list? Would it be

swix(OS_DoSomething, _INR(0,1) | _OUTR(1) | OUT(FLAGS), start, &end, thirdregister, &carry):

(I had some other questions too, but will try to find the C API for this)

Everything you need for _swi/_swix should be documented in swis.h.

All the output values should be placed after the input values in the parameter list.

Use _OUTR() if you are returning multiple registers, _OUT() for just one.

If you’ve specified _OUT(_FLAGS), , &flags will need to be at the end of the list as 15 > other registers.