cake VS ack

Cake is a C23 Front End http://thradams.com/cake/index.html that is implementing static ownership checks.

Cake source itself is already using this feature that can be used and disabled with few macros.

The link is a tour explaining the concepts and usage of this feature.

I have an open source project (https://github.com/thradams/cake) that can check coding style in case someone wants to help.

Actually this is suggestion for myself.(https://github.com/thradams/cake/issues/22)

# Compiling https://github.com/thradams/cake cmake_minimum_required (VERSION 3.20)

Here's the peephole optimiser file for the 68000 on the ACK, showing what kind of optimisations you can do: https://github.com/davidgiven/ack/blob/default/mach/m68020/top/table

The Amsterdam Compiler Kit: https://github.com/davidgiven/ack

Looking at the ACK assembler which dates from the 16-bit era (https://github.com/davidgiven/ack/tree/default/mach/proto/as), it seems to hold a bitfield which tells it whether variable-sized instructions have been shortened or not. Bits are only allocated for instructions which can change length. The downside is that if you have conditionals which turn on and off sections of source based on factors which can change from pass to pass, Very Bad Things happen because it doesn't keep a mapping of which bit corresponds to which instruction. Plus, an instruction can only be shortened once. IME a naive assembler needs multiple relaxation passes to get optimal results.

Here are some that are even older: https://github.com/davidgiven/ack/commits/default/Copyright

It's not strictly bare metal, but you might be interested in this: https://github.com/davidgiven/ack/blob/default/plat/pc86/boot.s It's the startup code for running C (and other languages) from a bootable floppy. It's known at boot time that you get at least 64kB of memory at 0x07c0:0000, so we just use that.

The 8080 is historically interesting, but in my personal opinion kind-of a rotten CPU to develop for... the assembly mnemonics came from a time when they haven't figured out a nice way to write them yet. Also, I don't think the CPU wasn't used in that many machines and it certainly isn't common now, and as a results compilers tend to be commercial and old. (One that is not commercial is the Amsterdam Compiler Kit, but good luck getting that to work, especially if you insist on Windows...) Generally compiled languages also tended not to be used that much around that time, the lingua franca still was assembly.