Skip to content

research: qualify Connect4 BSFP dominance on CUDA-JS alpha.20 - #82

Draft
iteathen wants to merge 6 commits into
mainfrom
research/connect4-bsfp-dominance-pair-refresh
Draft

iteathen wants to merge 6 commits into
mainfrom
research/connect4-bsfp-dominance-pair-refresh

Conversation

@iteathen

Copy link
Copy Markdown
Owner

Tracks #81.

This draft does not change Tensor's protected CUDA-JS compatibility identity. It adds:

  • a Connect4-BSFP-shaped device-callable Tensor matmul/reduction composition test for both minimal and maximal dominance directions;
  • a qualification-only PR workflow that stages CUDA-JS 98e2ebc942c14d63acf4dd82e912dd548c363a05 / 0.1.0-alpha.20 ephemerally in the runner and runs the complete Tensor verification suite.

The purpose is to falsify the exact-pair refresh before changing protected compatibility. Portable/mock success is not native/provider or performance evidence. If the staged pair exposes a missing/broken CUDA-JS mechanism, that lower-layer defect will be filed in CUDA-JS rather than worked around here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant