Freestanding environment about kotlin-native HOT 4 CLOSED

Probably such components better be written in C.

from kotlin-native.

Well, it's up to target platform how to link the final binary, so you could produce any image you like,
including a self-contained ELF or similar (see https://github.com/JetBrains/kotlin-native/blob/master/backend.native/compiler/ir/backend.native/src/org/jetbrains/kotlin/backend/konan/LinkStage.kt).

Regarding memory management - nothing prevents you from using automated MM in kernel environment as well, it's just a reference counter, most kernels do that themselves for some types of data. What you would need to implement for such a port is:

• custom malloc/free (better based on some buddy algorithm)
• custom address -> symbol mapper, if symbolic backtraces expected
• console output with print

IIRC, there's an effort in similar direction, see https://github.com/semoro/KOS

from kotlin-native.

Regarding memory management - nothing prevents you from using automated MM in kernel environment as well,

For memory mapped I/O and bootstrap structures to set up page tables, device driver ring queues on the NIC, etc, you need complete control. For some structures, refcount overhead is simply prohibitive.

from kotlin-native.

As K/N is being primarily an application development language, there's no plans to support such a feature.

from kotlin-native.