vx-lang / vx-lang/Vx

C3: switch vxc to compile_pipeline; retire the AST middle/back-end after soak

Open
#201 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Part of epic hiraditya/Vx.1#197. Roadmap:
docs/discussions/implementation_plans/flat_pipeline_convergence.md (C3). Depends on C2 (#200) at
parity.

Once C2 (#200) is at parity on the full suite:

  • vxc drives src/pipeline.rs::compile_pipeline; codegen consumes the flat streams + frozen
    registry.
  • The sequential AST middle/back-end moves behind --legacy-codegen for a soak.
  • The parallel verification hooks (parallel_architecture_verifier) run in debug.
  • After the soak, remove the AST middle/back-end.

This is the end state of the convergence: vxc production == the flat-array parallel pipeline, which
is the core architectural claim (docs/parallel_compiler_architecture.md). Fold in hiraditya/Vx.1#196 (assert
stream order determinism) before codegen depends on stream order.

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

Read docs/discussions/implementation_plans/flat_pipeline_convergence.md for C3, then inspect src/pipeline.rs::compile_pipeline and the architecture described in docs/parallel_compiler_architecture.md. Check C2 (#200) and the stream-order determinism work in hiraditya/Vx.1#196 before changing code. Done means vxc uses the flat pipeline, legacy codegen is available for the soak, debug verification hooks run, and the AST middle/back-end is removed afterward.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
compilers
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.