3 ms·
> Currently only stm8, z80, z180, gbz80, r2k, r3ka, tlcs90 SDCC backends supported this is pretty cool... the gameboy (gbz80) processor is supported. now we ca
by rkachowski 10y ago
> Currently only stm8, z80, z180, gbz80, r2k, r3ka, tlcs90 SDCC backends supported
this is pretty cool... the gameboy (gbz80) processor is supported. now we can make late 80s gameboy roms on any 2016 llvm supported language
- JoshTriplett 10y agoI'd love to see support for the 65c816/5A22, to allow targeting the SNES. Anyone know of Open Source compilers targeting that family of processors?
- astrange 10y agocc65 does support the NES: https://github.com/cc65/cc65 https://github.com/cc65/cc65 It might have an SNES mode too. Note that even the 65c816 isn't good enough to run most C and your "portable" C code probably isn't portable if int isn't 32 bits anymore!
- JoshTriplett 10y agoDoesn't look like it covers the SNES, unfortunately, but NES support helps. Rust recently gained support for systems with 16-bit integers and pointers, in order to support AVR. It'd be challenging, and some of the libraries might not work out of the box, but it's worth a shot. The much harder part would be supporting various memory windowing techniques.
- pcwalton 10y ago> Note that even the 65c816 isn't good enough to run most C At least they added stack-relative addressing, which is a huge improvement over the 6502.
- deleted 10y ago[deleted]
- mappu 10y agoI wrote a gameboy game using the (old) SDCC that ships with the (old) GBDK, and ran into countless issues with what i assume was the C frontend. Rearrange functions in source file? ICE! Reorder variable definitions? ICE! It was very cool to end up with a working .gb rom but the process was not a great experience. Hopefully this addresses some of the compiler reliability. EDIT: play my crappy game https://code.ivysaur.me/shmup/ https://code.ivysaur.me/shmup/