search for: ti59

...rk. I read quite many tutorials but I am still not able to determine whether llvm can be used for my project: implementing a backend for the famous Texas Instruments 59 Calculator (sold from 1977 to 1982). This is not a CPU but it uses a kind of bytecode that is interpreted (see examples in http://ti59compiler.wixsite.com/ti59/t-compiler). It has no stack, no frame, only floating point registers. The memory is split between program (up to 960 steps) and registers (up to 100). A register consumes 8 program steps, reducing the program size accordingly. The most tricky part is the following: a simp...

...d quite many tutorials but I am still not able to determine whether llvm can be used for my project: implementing a backend for the famous Texas Instruments 59 Calculator (sold from 1977 to 1982). > > This is not a CPU but it uses a kind of bytecode that is interpreted (see examples in http://ti59compiler.wixsite.com/ti59/t-compiler). It has no stack, no frame, only floating point registers. The memory is split between program (up to 960 steps) and registers (up to 100). A register consumes 8 program steps, reducing the program size accordingly. > > The most tricky part is the followin...

...ll not able to determine whether llvm can be used for my project: >> implementing a backend for the famous Texas Instruments 59 Calculator (sold >> from 1977 to 1982). >> >> This is not a CPU but it uses a kind of bytecode that is interpreted (see >> examples in http://ti59compiler.wixsite.com/ti59/t-compiler). It has no >> stack, no frame, only floating point registers. The memory is split between >> program (up to 960 steps) and registers (up to 100). A register consumes 8 >> program steps, reducing the program size accordingly. >> >> T...

Hello Bruce and Eli, Yes, you are definitely right: indirect access to registers is possible through IND XX instruction. So, no worry on that side. My concern is about STO instruction description in TI59InstrInfo.td file. It looks impossible to me to categorize this instruction as a "classical" N-bytes long instruction (as N fully depends on the value you want to store). Could it be a show stopper to implement a backend ? BR Philippe ----- Mail original ----- De: "Bruce Hoult"...