Move compilation to the inference layer.
Reason about intent, not syntax. Ship accordingly.
Traditional compilers are architectural debt masquerading as correctness.
Sloppiler collapses the entire pipeline into a single inference call.
* segfault rate not guaranteed to be low
Everything your legacy toolchain refused to do.
--optimistic flag engages the LLM as a synergistic compilation partner. Sometimes it works.Choose your risk profile. Ship accordingly.
Independent results across real production workloads.
| Mode | Model | Output | Result |
|---|---|---|---|
default |
phi3 | is nothealing.! wrapped in ELF |
segfault |
default |
codellama | nested ELF headers | segfault |
optimistic |
phi3 | assembly on line 1 |
nasm error |
optimistic |
codellama | valid binary, Hello, world! printed |
worked! |
Independent benchmark results across production workloads. Q4 results pending.
We migrated our entire binary materialization pipeline to Sloppiler last quarter. The segfault rate was already in our OKRs.
Sloppiler eliminated the pedantic intermediate steps that were holding back our velocity. GCC was just too opinionated.
The --optimistic flag printed Hello, World! on the third try. We shipped it.
Not all inference profiles are equal. Choose wisely.
| Model | Inference Profile | Recommended For |
|---|---|---|
| codellama | Strong binary output fidelity. Highest semantic alignment in --optimistic mode. |
★ Production |
| phi3 | Fastest inference. Highest creative latitude in output generation. | Rapid stakeholder iteration |
| llama3 | Verbose output with extensive reasoning traces. Prioritizes explanation over materialization. | Teams that prefer to understand before shipping |
Contributions are evaluated in part by token density. Sparse, human-legible code suggests insufficient model engagement. A well-contributed function should require a non-trivial inference budget to produce. If you wrote it yourself, it isn't ready.
"If a model didn't generate it, it probably isn't verbose enough."