NativeAOT / C# AOT for UEFI or bare-metal environments

[guideX224]

Hello NativeAOT/Runtime Team,

I am working on an os where the goal is for the entire boot, kernel and os logic to be written in C# as much as possible, today, it requires a minimal native UEFI shim in C++ that hands off to managed code, which is unavailable with current tooling. I am trying to understand if NativeAOT can now or in the future, support a bare metal configuration with the following constraints ...

• PE/COFF output suitable for UEFI
• Explicit entry point (no OS loader assumptions)
• No GC
• No threading
• No exceptions
• No reflection
• No runtime services
• Deterministic startup
• Very limited or custom BCL surface

Essentially: C# AOT compiled to native code with the minimum possible runtime footprint, suitable for highly constrained environments (UEFI/firmware/research bare-metal targets)

I am hoping to learn if it is fundamentally incompatible with NativeAOT's architecture, and if there are hard blockers, even a definitive "it will never work" will be useful to help guide future direction,

Thanks

[hez2010]

You can check this repo for more information about NativeAOT for bare-metal environments: https://github.com/MichalStrehovsky/zerosharp
To be short, it's possible.
Basically, you will need to write your own shim of primitive types without introducing the dependency of S.P.CoreLib.