No.
Actually, I can say more. The program was designed to have aminimal
access to the system services. As such, the majority of its parts
run with no system calls (even no explicit libc).
After initialization there is no memory allocated/freed. Only I/O
is fseek/fread/fwrite/fprintf. All non-printf is done in single
2KB block sizes (due to the internal cache).
'top' shows the program is 99.9% CPU most of the time.
I expect to have the machine available for testing this weekend (I
will do it earlier if I get access).
-- Eyal Lebedinsky (eyal@eyal.emu.id.au)