RossH,
There are "plain old PASM" modules used in the propgcc system especially the loader. They are assembled using BST but that is about to be swapped out for Roy's new open source Spin compiler which already produces identical code to the Prop tool (barring any bugs that will no doubt be fixed if they show up in the future)
Ok - I didn't know that. That would save some effort when porting the Catalina runtime to GCC.
No qualms with using the Catalina run time with GCC. However I feel that ever happens it should be independent of what propgcc is now. Perhaps even a separate project.
Yes, it seems like plugins and the use of a rendevous area should be separate from the compiler. These are things normally done by an OS or a simple driver manager. PropGCC allows for reserving space at the high end of memory, which can be used for a driver description table, or whatever the programmer wants to use it for.
I've done some work on integrating PropGCC programs with the spinix runtime services, but I haven't looked at it for 6 months. Basically, it just requires reserving space at the high end of memory and writing drivers that are compatible with PropGCC's filedriver structure. If the Catalina run time services could be packaged into a self-contained set of routines it should be possible to use it with PropGCC.
I'll have to dig around to find where it's documented. In spinix I just overwrite the initial stack pointer value in the hub memory image before I start up the cog. The SP starts at $8000 by default, but if you change it to a smaller number the C program won't use any memory beyond that value. I'm pretty sure the $8000 default value can be overwritten by the linker or loader if you explicity specify a new value.
Comments
Ok - I didn't know that. That would save some effort when porting the Catalina runtime to GCC.
Ross.
I've done some work on integrating PropGCC programs with the spinix runtime services, but I haven't looked at it for 6 months. Basically, it just requires reserving space at the high end of memory and writing drivers that are compatible with PropGCC's filedriver structure. If the Catalina run time services could be packaged into a self-contained set of routines it should be possible to use it with PropGCC.
It does? I seem to have missed something here. Where is this documented?
It's a simple linker thing, but I don't think it has been officially documented.