Another usecase for microC: most decompilers decompile to a custom C-like language. It pretends to be C, but in reality this is just a representation of a recovered AST that is often-but not always-a valid C code. MicroC would be a better target, because it would supposedly have less weird edge cases.
That depends on the assembly language. Some have structure constructs, some are typed. Portability is out.
But if you accept a slightly higher abstraction, WebAssembly is portable, typed, and structured.
Does WebAssembly support AOT compilation to native binaries? I thought it was just a VM.
Or use an existing implement like wasmedge, I guess.
If your goal is a simple language to compile, well, Rust won't ever fit the bill; but as a target for a decompiler, I think the unsafe subset is worth exploring.
And even before that release, there were macros the poly fill it, so you could have used those to target an earlier version.
It's definitely something I would like to see at least explored!
MASM and TASM, were already far beyond the features in K&R C, if we overlook the issue of being bound to 80x86 Assembly.
TI has some DSPs where their Assembly is basically bare bones C like, in a SSA kind of approach.
Wait... we have it... RISC-V.
But we need performant µArchitectures of all major use cases (server/desktop/mobile/etc) and that on the best silicon process.
If RISC-V is a success, no need for a µC, just go RISC-V assembly BUT... do not abuse that macro preprocessor, because if it is to move complexity from the C syntax to some macro preprocessor, that would be pointless.
I guess, we are looking for even simpler thas sphinx c--.
I start to wonder, if I could not express such simple C syntax using a powerful assembler macro preprocessor (like the one of fasm2). Until there is a "expression" processor, it should kind of be easier.