search for: dcpu16

> 16-bit byte was a major pain back in the day, and we never fixed all > known failures. In part, it's because C standard really wants 8-bit chars. So no real solution? > Btw, why is DCPU16 still a thing? :) https://github.com/techcompliant/. It's a separate team not related to Mojang which took the idea. They are on alpha now. Also because https://github.com/FrOSt-Foundation/cFrOSt ;)

Hi. I'm working on a backend for the [DCPU16](https://github.com/techcompliant/TC-Specs/blob/master/CPU/DCPU.md), a fictional CPU. The main subtlety is that the bytes are 16 bits instead of 8. There is already a [working backend](https://github.com/krasin/llvm-dcpu16), but it does a lot of source modification to support 16 bit words. I tr...

Hi, I'm with a team using 16-bit bytes for an out-of-tree target. The AsmPrinter framework's implementation of the DWARF debugging format is not very good at distinguishing between target-sized bytes (which is the more common use) and 8-bit-bytes. The DWARF standard itself seems not very good in this regard, actually. So we have had to hack our way around this. I.e., at some call-sites of