A retargetable c compiler design and implementation

#A retargetable c compiler design and implementation code#
#A retargetable c compiler design and implementation simulator#

The PDP11 doesn't really have enough registers (8, with 5 or 6 available), and the others double this in different ways. PDP11, MSP430, M68k/Coldfire, SH4 form a kind of family of ISAs that are quite pleasant to program in assembly language and relatively easy to write a decent compiler for. I thought a lot of these text based games had been ported to the Z80 (with CP/M?). Maybe a week if there is any desire to have a listing. An assembler for a custom CPU could be written in Python in a couple of days.

#A retargetable c compiler design and implementation code#

One alternative might be to manually convert the C code to asssembly language. The compiler becomes the project and that isn't the original goal. Don't forget, the emitted code has to pass the regression tests - all of them! But even the tests need to be retargeted.

We're talking about man-years of work (as a guess) to get that C compiler running. To that end, I would avoid designing a custom CPU.

BDS C Compiler (started in 1979) for the 8080/Z80 Short answer: I would avoid retargeting a compiler at any cost. The T80 initially came up because I wanted to recreate PacMan - in fact, PacMan got me started in this adventure with FPGAs. Pretty cool to watch that old dog feed files to something like an FPGA Z80 CPU. Ultimately, I had Kermit running and I transferred the bulk of the files from a CompuPro (real) Z80 which used 8' floppies. In fact, I used the 22Nice Z80 emulator, running on a PC, to allow use of the Digital Research Macro Assembler to write the BIOS. A really fast Z80! Again, I picked a CPU for which tools already exist. It was as easy as adding a Compact Flash to the bus, writing the BIOS code, loading the disk image (I forget how I did that, today I would use Linux 'dd') and it was up and running. It is a cycle accurate Z80 and I used it to implement CP/M (and friends) on a Spartan 2 about 15 years ago. To that end, I recommend the T80 core at. It would be far better to pick a CPU (like the Z80) for which tools already exist (CP/M, C, Macro Assembler, FORTRAN, PL/I). For mere mortals, goal 3 is out of the question which kills goal 2. There are competing goals: 1) Play the games, 2) invent a CPU and 3) retarget a compiler. Berkeley Sockets works well! Somehow, that seems really important, to me. I have no particular application but I do have a web server on each (yet to have any interesting content). I have two of these machines and I really enjoy writing little code snippets in C, Pascal or FORTRAN.

#A retargetable c compiler design and implementation simulator#

It is based on a Raspberry pi with the SIMH simulator package simulating the PDP-11/70. Well, there is the PiDP-11-70 which is a really good emulation and runs several operating systems including BSD 2.11 which is very similar to BSD 4.3. Many of the text based games were available on the PDP-11/70. Designing compilers is not a job for mere mortals. LCC started out as a compiler specifically for retargeting so it may be a great deal easier to modify than SDCC, That's why I would pick a CPU for which a toolchain already exists. SDCC doesn't seem to be over-friendly in that area and I haven't tried retargeting LCC. A couple of man-weeks to design and implement a CPU in an FPGA but from what I see, man-years to retarget the compiler.