Backend spike: Cranelift vs LLVM vs C transpilation
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Read ADR-0002 and locate the KIR VM, the example suite, and the fib.kin example. Build throwaway spikes for Cranelift, LLVM, and C transpilation, then benchmark each against the VM. Done means the ADR contains comparison numbers, records the backend choice, and the chosen backend compiles the example suite.
Written by the indexing model from the issue text.
Description
ADR-0002 decision milestone. Build three throwaway spikes that compile fib.kin to native and benchmark against the KIR VM; write the decision ADR; pick one for production.
Acceptance: comparison numbers in the ADR; chosen backend compiles the example suite.
- Dominant language
- Rust
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from kokernk-ctrl/KINN
-
P-008 tooling
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
kokernk-ctrl/KINN#10 ·
-
compiler P-002
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
kokernk-ctrl/KINN#6 ·
-
docs P-012 security
Difficulty 5/5 Over a week Newbie friendliness 25/100
kokernk-ctrl/KINN#11 ·
-
P-005 studio
Difficulty 4/5 3-5 days Newbie friendliness 48/100
kokernk-ctrl/KINN#9 ·
-
compiler P-006 P-007 studio
Difficulty 5/5 Over a week Newbie friendliness 35/100
kokernk-ctrl/KINN#8 ·
All issues in kokernk-ctrl/KINN
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
DecapodLabs/decapod#1871 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 76/100
416rehman/Guardrails#1716 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
dginev/latexml-oxide#943 ·
Maintainers usually reply within 1 day
-
area:core area:python task
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
area:stdlib effort:S impact:med platform:linux type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day