Size trimming

[suborb]

Hope you don't mind, I'm just going to drop some hints on size trimming at link time.

• Adding -Cl-v will show all the library routines being linked in

From this I can see a lot of printf formatters being pulled in. You can configure which ones are pulled in by adding the following to zpragma.inc:

#pragma printf "%s %02d %c %u"

Which probably covers most of the cases you've got, this will save a few hundred bytes. You can do the same with the scan formatters (#pragma scanf)

• The CP/M file handling is rather heavyweight, if you don't need file routines for a binary then add -lndos to the linking options will replace them with stubs. This will save 4k or so. If it gets really tight, I'm sure we could write a simplified version that would be a lot smaller.

Some compile time ones that may not be obvious:

• htons/htonl should be available in the standard library via <net/hton.h> - the peepholer additionally has some rules to handle these so you end up with both a performance and size advantage.

• If your hardware ports are known at compile time then using __sfrs will inline the IO code, saving time and size.

[jayacotton]

Thanks for the tips. I used the pragma printf and scanf to cut about 1k of code space.

[suborb]

No worries, one other thing, --c-code-in-asm will prevent some of the optimisation rules from firing so you might want to consider removing that at some point.

[jayacotton]

More thoughts on this aspect of the project.

1. Implement all of the above as it applies.
2. The code assumes that each app is standalone, this may not be true in all cases.
3. implement an overlay or subdivide the tasks, i.e. ifconfig could configure all the required network attachments and leave only socket and to the app.