In 2020 we are all allowed to be grumpy!
Its not my biggest concern (bytewise IO is that) but it is an example where a s/370 assembler guru could spend 10 mins to smash it. Even in C I would try and do it dword by dword ...
For any application we port that uses calloc() it would make a difference.
But as you say if a magic answer doesn't appear soon, we have a functional bit of code.
We are making progress: atexit, signals (which sounds like it will have to be internal to gcclib), longjmp and we have cleared the remaining non-RESLIB detritus. Dynamic stack, svc202 work arrounds, Io optimisations and we have a baseline. Then housekeeping like automatic reslib stub generation and MOST important automatic testing.
(Ok a bit to do!)
