mirror of
https://github.com/irmen/prog8.git
synced 2024-10-17 10:24:55 +00:00
90 lines
2.4 KiB
ReStructuredText
90 lines
2.4 KiB
ReStructuredText
====
|
|
TODO
|
|
====
|
|
|
|
Memory Block Operations integrated in language?
|
|
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
|
|
|
@todo list,string memory block operations?
|
|
|
|
- list operations (whole list, individual element)
|
|
operations: set, get, copy (from another list with the same length), shift-N(left,right), rotate-N(left,right)
|
|
clear (set whole list to the given value, default 0)
|
|
|
|
- list operations ofcourse work identical on vars and on memory mapped vars of these types.
|
|
|
|
- strings: identical operations as on lists.
|
|
|
|
these should call (or emit inline) optimized pieces of assembly code, so they run as fast as possible
|
|
|
|
For now, we have the ``memcopy`` and ``memset`` builtin functions.
|
|
|
|
|
|
|
|
More optimizations
|
|
^^^^^^^^^^^^^^^^^^
|
|
|
|
Add more compiler optimizations to the existing ones.
|
|
|
|
- on the language AST level
|
|
- on the StackVM intermediate code level
|
|
- on the final assembly source level
|
|
- can the parameter passing to subroutines be optimized to avoid copying?
|
|
|
|
- subroutines with 1 or 2 byte args (or 1 word arg) should be converted to asm calling convention with the args in A/Y register
|
|
|
|
|
|
Also some library routines and code patterns could perhaps be optimized further
|
|
|
|
|
|
Eval stack redesign? (lot of work)
|
|
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
|
|
|
The eval stack is now a split lsb/msb stack using X as the stackpointer.
|
|
Is it easier/faster to just use a single page unsplit stack?
|
|
It could then even be moved into the zeropage to greatly reduce code size and slowness.
|
|
|
|
Or just move the LSB portion into a slab of the zeropage.
|
|
|
|
Allocate a fixed word in ZP that is the TOS so we can operate on TOS directly
|
|
without having to to index into the stack?
|
|
|
|
|
|
More flexible (non-const) arrays?
|
|
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
|
Currently, array literals can only be constants
|
|
Allow for non-const arrays? Such as::
|
|
|
|
ubyte[16] block1
|
|
ubyte[16] block2
|
|
ubyte[16] block3
|
|
ubyte[3] blocks = [block1, block2, block3]
|
|
|
|
|
|
structs?
|
|
^^^^^^^^
|
|
|
|
A user defined struct type would be nice to group a bunch
|
|
of values together (and use it multiple times). Something like::
|
|
|
|
struct Point {
|
|
ubyte color
|
|
word[3] vec = [0,0,0]
|
|
}
|
|
|
|
Point p1
|
|
Point p2
|
|
Point p3
|
|
|
|
p1.color = 3
|
|
p1.vec[2] = 2
|
|
|
|
|
|
Misc
|
|
^^^^
|
|
|
|
- sqrt() should have integer implementation as well, instead of relying on float SQRT for all argument types
|
|
- code generation for POW instruction
|
|
- are there any other missing instructions in the code generator?
|
|
- implement %asmbinary
|