From bf67f5fc29459876e72a25e51bf11633bf75c9a2 Mon Sep 17 00:00:00 2001 From: Mark Canlas Date: Tue, 16 Jan 2024 19:26:46 -0500 Subject: [PATCH] register allocation --- TODO.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/TODO.md b/TODO.md index a8fc0f7..fdc8b7a 100644 --- a/TODO.md +++ b/TODO.md @@ -1,5 +1,8 @@ -- it would be cool for the generated code writer to go to files - - and make the +1 methods optional (for when it is at max) +- normalize A, X, Y, ZP, and GP to "registers", allocated by an allocator + - X and Y are also index registers, so slightly special + - unit test: what if a for loop is three deep? the outermost loop must be a memory register +- it would be cool for the 22-tuple Scala code generator code writer to go to files + - and make the +1 methods optional (for when it is at max == 22) - the payload/`xs` of a program should be an ADT of either chunks or one instruction - where a chunk is just many instructions - and an instruction already has the value X with its encoder, but chooses an eternal mode