1
0
mirror of https://github.com/hsoft/collapseos.git synced 2025-04-05 21:08:46 +11:00
collapseos/apps
Clanmaster21 9797405789
Major parsing optimisations
Totally reworked both parseDecimal and parseDecimalDigit
parseDecimalDigit no longer exists, as it could be replaced by an inline alternative in the 4 places it appeared. This saves one byte overall, as the inline version is 4 bytes, 1 byte more than a call, and removing the function saved 5 bytes. It has been reduced from between 52 and 35 cycles (35 on error, so we'd expect 52 cycles to be more common unless someone's really bad at programming) to 14 cycles, so 2-3 times faster.
parseDecimal has been reduced by a byte, and now the main loop is just about twice as fast, but with increased overhead. To put this into perspective, if we ignore error cases:
For decimals of length 1 it'll be 1.20x faster, for decimals of length 2, 1.41x faster, for length 3, 1.51x faster, for length 4, 1.57x faster, and for length 5 and above, at least 1.48x faster (even faster if there's leading zeroes or not the worst case scenario).
I believe there is still room for improvement, since the first iteration can be nearly replaced with "ld l, c" since 0*10=0, but when I tried this I could either add a zero check into the main loop, adding around 40 cycles and 10 bytes, or add 20 bytes to the overhead, and I don't think either of those options are worth it.
2019-10-13 13:50:07 +01:00
..
at28w zasm: rename #inc to .inc 2019-10-06 14:32:23 -04:00
ed Fix misc. source comment typos 2019-10-09 11:12:08 -04:00
lib Major parsing optimisations 2019-10-13 13:50:07 +01:00
memt zasm: rename #inc to .inc 2019-10-06 14:32:23 -04:00
sdct zasm: rename #inc to .inc 2019-10-06 14:32:23 -04:00
zasm Fix misc. source comment typos 2019-10-09 11:12:08 -04:00
README.md Make userspace parse args the same way the shell does 2019-06-02 14:05:20 -04:00

User applications

This folder contains code designed to be "userspace" application. Unlike the kernel, which always stay in memory. Those apps here will more likely be loaded in RAM from storage, ran, then discarded so that another userspace program can be run.

That doesn't mean that you can't include that code in your kernel though, but you will typically not want to do that.

Userspace convention

We execute a userspace application by calling the address it's loaded into. This means: a userspace application is expected to return.

Whatever calls the userspace app (usually, it will be the shell), should set HL to a pointer to unparsed arguments in string form, null terminated.

The userspace application is expected to set A on return. 0 means success, non-zero means error.