{"id":1351,"date":"2020-02-06T20:30:23","date_gmt":"2020-02-06T20:30:23","guid":{"rendered":"http:\/\/retroramblings.net\/?p=1351"},"modified":"2020-02-08T15:15:16","modified_gmt":"2020-02-08T15:15:16","slug":"time-to-stop-being-lazy","status":"publish","type":"post","link":"https:\/\/retroramblings.net\/?p=1351","title":{"rendered":"Time to stop being lazy!"},"content":{"rendered":"\n

The EightThirtyTwo ISA – Part 15 – 2020-02-06<\/strong><\/p>\n\n\n\n

I’ve joked a few times in this series about being too lazy to write an assember – but it would be more true to say that the stop-gap solution I was using was adequate, so my time was better spent on the more enjoyable aspects of the project. I am now feeling the limitations of using the GNU assembler to produce a bytestream for a target it knows nothing about, and to improve either the performance or code density of the vbcc backend’s output any further, I need to address the problem I’ve had so far with cross-module references…<\/p>\n\n\n\n\n\n\n\n

The most efficient way to reference a symbol with the 832 architecture is to use successive “li” instructions to build a PC-relative offset six bits at a time. That’s fine if the reference and its target are in the same source module and section, since then the offset is fixed, and can’t change during the linking process. The problem is with cross-module references, since we then have a link-time determined value to be broken up into six-bit chunks and inserted into successive ‘li’ instructions. <\/p>\n\n\n\n

That’s not possible with the current solution, so I’m currently using a less efficient method, a ‘ldinc r7’ instruction followed by an inline 32-bit reference. This works fine but is a bit of a performance drag since it causes the instruction prefetch to be flushed as the program counter skips over the inlined constant, then triggers a separate load for that constant. Worse still, since the instruction stream is a stream of bytes, there’s no alignment guarantee for the loaded reference, so on average three out of four such references will require two loads!<\/p>\n\n\n\n

For this reason, the time has come to write not only an assembler, but a linker too.<\/p>\n\n\n\n

The options are to adapt an existing project or start from scratch, and I’m likely to learn more from the latter option, so that’s my plan. While my first instinct when tackling this kind of project would be to reach for C++, I’m actually going to use plain C this time, simply because it would be nice if the toolchain could eventually be self-hosting, and I don’t imagine a C++ compiler for 832 will come into existence any time soon!<\/p>\n\n\n\n

So in the interests of keeping things as simple as possible I have defined a new object file format specifically for 832 consisting of…:<\/p>\n\n\n\n