Moved to Kick Assembler - you need to place KickAss.jar into 'assembler' directory. Unfortunately, it's not present anywhere on the GitHub, so I can't add it as a submodule.
New tool for placing routines. More advanced algorithm (can still be improved if there is need), prints out two log files into build/target_* directory for debugging purposes - I hope comments in the code (KS function in build_segment.cc) are sufficient. Tool is more flexible now - can accept multiple directories as input, single files can be given too (or a mix of files and directories).
Some very minor changes - this was definitely a toolchain sprint.
All similarities length >3 explained in the last commit - unfortunately, a new routine placing algorithm spawned A LOT of them, most having RTS in the middle :/
Moved to Kick Assembler - you need to place KickAss.jar into 'assembler' directory. Unfortunately, it's not present anywhere on the GitHub, so I can't add it as a submodule.
New tool for placing routines. More advanced algorithm (can still be improved if there is need), prints out two log files into build/target_* directory for debugging purposes - I hope comments in the code (KS function in build_segment.cc) are sufficient. Tool is more flexible now - can accept multiple directories as input, single files can be given too (or a mix of files and directories).
Some very minor changes - this was definitely a toolchain sprint.
All similarities length >3 explained in the last commit - unfortunately, a new routine placing algorithm spawned A LOT of them, most having RTS in the middle :/