New multi-core kernel for AmigaOS 4 shown at Pianeta Amiga!

@sofistisoftware

clib2 is old and outdated, use clib4..
i use newlib, just because I'm not porting anything, and it's the default.

@LiveForIt

Then again, my ports, or compilations, typically used newlib, because I wasn't all that knowledgeable and it was easier for me than to try to use clib2, which apparently required changing some things.

@afxgroup
Quote:Additionally to the obsolete, AmigaOS 0.x-3.9/m68k **4 way to get SysBase next to no AmigaOS 4.x software uses, other things you wrote are wrong as well, for example
Quote:No, it doesn't.
All normal programs and tasks are running in user mode.
99% of the ExecSG kernel is running in user mode as well, only some tiny parts of it requiring it (accessing privileged special registers, MMU changes, exceptions, probably the task scheduler, etc.) are running in supervisor mode.

However, there is nothing in ExecSG preventing anything from executing some code in supervisor mode using IExec->SuperState()/IExec->UserState() or IExec->Supervisor().
And some software you might not expect to use supervisor mode could do, for various reasons. Hint: Make sure not to have any SFS partitions mounted when testing your quarantine mode

@sofistisoftware
Quote:Using clib2 with it tons of bugs would be a nightmare
Anything is better than clib2, even libnix, which I ported to OS4 and used for all of my AmigaOS 4.x software before I ported newlib. The vclib C library is better as well if you use VBCC instead of GCC.
@afxgroup's clib4 will probably get usable some day, or maybe even already is, but the original clib2? Avoid using it at all costs on AmigaOS 4.x.

@joerg

Don't worry about it everything can be recreated this days.

@joerg

Quote:
Perhaps I'm missing something, but there seems to be at least one exception to that- printer drivers. Printer drivers are loaded and started by the printer device, so there is no startup code. And the only thing the printer device passes to the driver's initialization function is a pointer to a PrinterData struct.

That struct contains an embedded DeviceData struct, which in turn has a field called dd_ExecBase that seems to be just what we need. But testing shows that this field is always NULL. Maybe that's a printer device bug, but it seems to leave reading AbsExecBase as the only way to initialize SysBase.