vx-lang / vx-lang/Vx

Wire the Runtime

Open
#25 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

codegen enhancement runtime
Dominant language
Rust
Stars
14
Forks
2
Avg merge
12h 42m
Merged PRs (30d)
61

Description

Have the compiler emit LLVM IR calls to the C-ABI (vx_plugin_dispatch_async) when it encounters the spawn on block boundaries.

Sub-tasks

  • Link the generated LLVM IR to the C-ABI runtime (vx_hardware_runtime).
  • Emit calls to vx_plugin_dispatch_async for the binary payloads returned by the hardware plugins.
  • Emit calls to vx_plugin_alloc_and_transfer for .to_device() operations.
  • Emit vx_plugin_await_future and vx_plugin_transfer_device_to_host when variables are pulled back to .to_host().

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start by locating the compiler's LLVM emission for spawn on block boundaries and the runtime declarations for vx_hardware_runtime. Trace how binary plugin payloads, .to_device(), and .to_host() are represented before adding the corresponding ABI calls. Done means generated IR links to the runtime and emits dispatch, allocation/transfer, await, and device-to-host calls for those cases.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, rust
Domain
backend, compilers
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.