Kompile should produce both the llvm binary and the llvm library at the same time

Open
#4,126 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
compilers

Research direction

Start with the Kasmer configurations in kbuild.toml, comparing llvm-kompile-type='c' with backend='llvm'. Trace how each kompile is invoked and determine which computation can be shared; done means one kompile produces both the LLVM library and binary without repeating that work.

Written by the indexing model from the issue text.

Description

Kasmer compiles its semantics both as a llvm library (llvm-kompile-type='c' and backend='llvm' in kbuild.toml) and as a binary (backend='llvm'). Each of these takes ~6 minutes. I'm assuming that most of the computation is identical for the two.

It would be nice if I could kompile both at the same time, in order to reduce compilation time.

Dominant language
Python
Stars
591
Forks
163
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from runtimeverification/k

All issues in runtimeverification/k

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.