RISC OS 64bit OSLib

Charles Ferguson gerph at gerph.org
Sun Dec 22 18:24:06 GMT 2024


On Mon, 18 Nov 2024, Charles Ferguson wrote:

> Hiya,
>
> As you may know, I've built a version of OSLib that is intended to work
> with 64bit RISC OS - https://github.com/gerph/riscos64-oslib. However,
> the code it generates isn't great, and there are a number of things that
> it doesn't do correctly - large numbers of input registers, processor
> flags, and some of the odd interface definitions that I don't understand.
> Oh and it doesn't handle the value returning versions of the interfaces,
> only the error reporting ones (ie x-prefixed calls).
>
> I'm intending to continue developing and improving it, but there is
> always limited time.
>
> Is there anyone who is interested in updating the original OSLib to
> build for RISC OS 64?

I'm guessing that there's little interest in this, given by the lack of
response. However, even if people aren't interested in it, I'll be
continuing working on it.

Additionally there is a processed collection of information in the OSLib
parser repository which I've just released -
https://github.com/gerph/riscos-oslib-parser/releases/tag/v0.01

This contains generated information for:

* SWI conditions (entry, exit, naming, conditionals).
* NVRAM constant names
* RISC OS Pyromaniac PyModule templates
* Constants
* RISC OS Pyromaniac API templates
* AArch64 interface generation (from the above repo)
* RISC OS Python SWI templates - not quite right yet
* Structures ('wimp messages') - not quite working yet

These are used in RISC OS Pyromaniac and other projects (like my
disassembler) to describe the interfaces of the system.

If anyone wants to improve them, or finds them useful, please let
me know.

--
Charles Justin Ferguson
[ My thoughts are my own. And sometimes they're not even sane. ]



More information about the oslib-user mailing list