Home /Modules/compiler/LANGUAGE.FORMAT.REFERENCE.md

LANGUAGE.FORMAT.REFERENCE.md

lib/compiler/LANGUAGE.FORMAT.REFERENCE.md · 96 line(s) · markdown

<p align="center"><img src="https://github.com/mearvk/SLeeLa/blob/master/images/sleela/sleela-compiler-logo-001.jpeg" alt="SLeeLa Compiler" width="100%"></p>

SLeeLa Compiler Language, Program, and Binary Format Reference

Max Rupplin - MEARVK LLC - 2026

This document is the native reference catalog for the SLeeLa Compiler. It records known language names, common producer programs, source extensions, intermediate/object representations, executable formats, operating-system associations, and safety considerations.

Reference rule

These mappings are recognition and planning references, not execution permissions. A name, extension, magic value, compiler signature, or format match never authorizes execution, loading, linking, installation, or native calls.

Language and producer mappings

Language / familyCommon producer programsSource formsCommon intermediate / object formsCommon executable / package forms
SLeeLaSLeeLa Compiler / SLeeLa VM toolchain.sleela, .sleela-script, .sldocumentSLIR, SLVMSLVM / project-defined artifacts
CGCC, Clang, MSVC, ICC/ICX.cLLVM IR, assembly, objectELF, PE/COFF, Mach-O
C++GCC/G++, Clang++, MSVC, ICC/ICX.cc, .cpp, .cxxLLVM IR, assembly, objectELF, PE/COFF, Mach-O
Objective-CClang.mLLVM IR, objectMach-O, ELF, PE/COFF where supported
Objective-C++Clang.mmLLVM IR, objectMach-O, ELF, PE/COFF where supported
Rustrustc.rsLLVM IR, objectELF, PE/COFF, Mach-O
Gogo build / cmd/compile.goGo object/internal IRELF, PE/COFF, Mach-O
Swiftswiftc.swiftSIL, LLVM IR, objectMach-O, ELF, PE/COFF where supported
FortranGCC/gfortran, LLVM Flang, Intel Fortran.f, .f90, .f95, .f03, .f08LLVM IR, objectELF, PE/COFF, Mach-O
AdaGNAT.adb, .adscompiler IR, objectELF, PE/COFF, Mach-O
DDMD, LDC, GDC.dLLVM IR/object or compiler objectELF, PE/COFF, Mach-O
Zigzig.zigLLVM IR/object or native objectELF, PE/COFF, Mach-O
AssemblyNASM, YASM, GAS, MASM.asm, .sobjectELF, PE/COFF, Mach-O
Pascal / Object PascalFree Pascal, Delphi.pas, .ppobjectELF, PE/COFF, Mach-O
COBOLGnuCOBOL and other toolchains.cob, .cblobject / compiler-specificELF, PE/COFF and vendor-specific forms
Javajavac, Eclipse compiler.javaJVM class files, JARJVM class/JAR
Kotlinkotlinc.kt, .ktsJVM class/JAR, Kotlin metadataJVM class/JAR; native targets vary
Scalascalac.scalaJVM class/JARJVM class/JAR
C#csc, dotnet.csIL/.NET metadataPE/.NET assembly
F#fsc, dotnet.fs, .fsi, .fsxIL/.NET metadataPE/.NET assembly
Visual Basic .NETvbc, dotnet.vbIL/.NET metadataPE/.NET assembly
PythonCPython, PyPy.pybytecode / implementation-specific IR.pyc and packaged forms
JavaScriptNode.js, browsers, JS engines.js, .mjs, .cjsengine bytecode/JIT artifactssource/package/bundle
TypeScripttsc, bundlers.ts, .tsxJavaScript / source mapsJS packages/bundles
Rubyruby, JRuby, TruffleRuby.rbVM-specific bytecode/JITsource/package/implementation-specific
PHPphp, Zend tooling.phpVM bytecode/opcachesource/package/implementation-specific
Lualua, luac.luaLua bytecode.luac
HaskellGHC.hs, .lhsGHC Core/STG, LLVM/native objectELF, PE/COFF, Mach-O
OCamlocamlc, ocamlopt.ml, .mlibytecode/native objectELF, PE/COFF, Mach-O
Erlangerlc.erl, .hrlBEAM bytecodeBEAM modules/releases
Elixirmix/elixirc.ex, .exsBEAM bytecodeBEAM modules/releases
WebAssemblywasm toolchainslanguage-dependentWASM modules.wasm
LLVM IRLLVM language frontends.llLLVM IRtarget object/executable after lowering

Program-to-format reference

GCC/G++, Clang/Clang++, MSVC, rustc, Go, swiftc, GNAT, DMD/LDC/GDC, zig, NASM/YASM/GAS/MASM, Free Pascal/Delphi, javac, kotlinc, scalac, csc/dotnet, CPython/PyPy, GHC, OCaml tooling, BEAM tooling, and luac are represented as producer references.

Mappings are many-to-many: a language does not uniquely determine an executable format, and an executable format does not uniquely determine a source language.

Known native binary / executable / object formats

FormatFamilyTypical roleTypical OS / platform evidence
ELFExecutable and Linkable Formatexecutable, shared object, object, coreUnix-like systems, including Linux
PEPortable Executableexecutable, DLL, driver-related imageWindows
COFFCommon Object File Formatobject and PE-related structuresWindows/toolchain-specific and historical Unix variants
Mach-OMach Objectexecutable, dylib, objectApple platforms
a.outhistorical executable/objectexecutable/objecthistorical Unix systems
ARarchivestatic library/object archiveUnix/toolchain ecosystems
WebAssemblyWASM moduleportable sandboxed executable modulebrowser/runtime/embedded environments
JVM ClassJVM bytecodemanaged class artifactJava/JVM
JARZIP-based Java archiveJVM application/library packageJava/JVM
.NET assembly / PEmanaged assemblyIL + metadata.NET
BEAMErlang VM artifactmanaged bytecode moduleErlang/BEAM
Lua bytecodeLua VM artifactmanaged bytecodeLua runtimes
LLVM bitcodecompiler IRintermediate representationLLVM ecosystem
raw binaryno universal containerfirmware, flat image, extracted payload, or unknownplatform inferred from evidence

Safety considerations

  1. Inspect before executing. Reference databases are for classification, not execution.
  2. Treat binaries as untrusted input. Parsing must be bounded and memory-safe.
  3. Do not execute constructors, entry points, loader code, or embedded scripts during compilation analysis.
  4. Do not equate file extension with identity. Consider headers, sections, relocations, imports/exports, ABI markers, architecture, and compiler metadata together.
  5. Preserve conflicting evidence rather than silently choosing one identity.
  6. Require architecture and OS agreement before native-target assumptions.
  7. Separate managed bytecode from native machine code.
  8. Verify provenance, signatures, and checksums where policy requires them.
  9. Never bypass SLeeLa capability, resolver, memory, certificate, or VM boundaries.
  10. Compilation is not execution. Later native execution must cross an explicit SLeeLa security and VM policy boundary.

Compiler selection model

language name -> language family -> version -> producer program -> source form -> IR/object model -> target architecture -> target OS/ABI -> executable/package format

Unknown or conflicting mappings remain unresolved and are surfaced in diagnostics rather than silently guessed.

SLeeLa — MEARVK LLC — 2026