Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Define a package contract for multi-dispatch execution graphs

未关闭
  • 哪里不对？
#39 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
30/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
冷清
技术栈
cpp
领域
compilers

调研方向

Start by mapping the public package schema and C++ data model to the proposed versioned execution graph, then review package verification and inspection entry points. Define the graph, resource, node, dependency, and diagnostic coverage described in the acceptance criteria. Done means deterministic round-tripping, validation tests for each listed failure, inspection counts and diagnostics, and a one-node compatibility fixture without a host scheduler.

由索引模型根据 Issue 内容生成。

描述

Problem

Compiler packages describe compiled artifacts, reflection, validation, and source metadata, but they cannot represent an operation that dispatches multiple artifacts over shared resources with explicit ordering and visibility requirements.

Repository runtimes commonly sequence initialization, transformation, reduction, scan, FFT, and aggregation kernels through temporary buffers. Treating each artifact as an independent package entry loses the resource lifetime, dependency, and synchronization contract needed by package verification and downstream runtime tooling.

Expected behavior

  • Define a versioned, target-neutral execution graph document that can be embedded in or referenced by a compiler package.
  • Represent graph-scoped external inputs, external outputs, and temporary resources with logical type, physical layout, allocation size/alignment, and lifetime.
  • Represent dispatch, copy, fill, and barrier nodes with stable IDs and explicit dependency edges.
  • Resolve dispatch nodes to packaged artifact identity, entry point, specialization values, resource binding coordinates, and dispatch geometry.
  • Express resource access and memory visibility without encoding one target API's barrier enum.
  • Permit conditional or repeated execution only when the control resource and finite bound are explicit; arbitrary host callbacks remain outside the portable contract.
  • Preserve source/provenance metadata for graph nodes and referenced artifacts.
  • Extend package verification and inspection to reject missing artifacts, missing interfaces, incompatible resource layouts, invalid ranges, dependency cycles, unordered conflicting accesses, and unsupported graph capabilities.

Acceptance criteria

  • The public package schema and C++ data model round-trip a deterministic two-dispatch graph.
  • Package verification checks every referenced artifact, entry point, resource binding, and physical layout before reporting the graph ready.
  • Validation tests cover missing references, duplicate IDs, dependency cycles, unsafe barriers, invalid temporary lifetimes, and bounded-control errors.
  • Package inspection reports graph/node/resource counts, readiness, and structured diagnostics.
  • A compatibility fixture demonstrates that a single packaged compute artifact can be represented as a one-node graph without changing existing package consumers.
  • The contract is documented as metadata and verification; it does not claim a built-in host scheduler or native runtime executor.

Real-world driver

At MLX commit 4367c73b60541ddd5a266ce4644fd93d20223b6e, operations including reductions, scans, FFTs, split-kernel matrix multiplication, and quantized paths sequence multiple compute pipelines and temporary allocations. CrossTL issue CrossGL/crosstl#1736 is implementing the translator-side repository-neutral graph and runtime validation needed to exercise these paths on DirectX and OpenGL. A compiler package contract would let both repositories exchange the same artifact and graph identities without making the translator depend on a compiler release.

主要语言
C++
星标
0
派生
0
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

CrossGL/compiler 的其他 Issue

查看 CrossGL/compiler 的全部 Issue

相似的 Issue

更多 C++ Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。