I haven't made much progress on my attempt to write my own target for SDCC yet. Mostly because I sat down and re-designed my CPU from the bottom up. Mostly in the instruction set and not really in the architecture itself, although it is now primarily a 16-bit CPU with instructions for interacting with 8-bit data. It still has 16 registers and a full 64Kb of RAM. (Although I do have a simple MMU with paging I am designing.) I also still have a specific push and pop instruction although I am thinking of replacing that and dedicating one of my registers as the Stack Pointer if that makes things easier.
Is there a simple way to know what is required (like what functions and files are actually required in a target.) to have a valid target? On Thu, Nov 12, 2020 at 12:39 PM Bill Gaylord <chibill...@gmail.com> wrote: > I was looking at LLVM at first but its documention on writing a new back > is crazy complex and doesnt explain much. > > I have a working python emulator also working on one in C. Not sure if > that helps at all. > > On Thu, Nov 12, 2020, 7:16 AM Philipp Klaus Krause <p...@spth.de> wrote: > >> Am 12.11.20 um 13:48 schrieb Ralph Doncaster: >> > I found the code generators for libfirm/cparser a lot easier to follow >> > than gcc. >> >> A yes, I forgot to mention the Firm compiler. That one might indeed be >> another alternative. >> >> Philipp >> >> >> _______________________________________________ >> Sdcc-user mailing list >> Sdcc-user@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/sdcc-user >> >
_______________________________________________ Sdcc-user mailing list Sdcc-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sdcc-user
