Repository navigation
Conversation
|
Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
mdboom
left a comment
There was a problem hiding this comment.
A bunch of changes here seem to be moving to new precommit linter/formatter rules. That is fine, but we should re-enable the running of pre-commit on these files in this PR as well if that's the case. (It was disabled on the cuda_bindings_12 directory in the previous PR in this stack).
| ctypedef int BOOL | ||
|
|
||
| cdef DWORD LOAD_LIBRARY_SEARCH_SYSTEM32 = 0x00000800 | ||
| const DWORD LOAD_LIBRARY_SEARCH_SYSTEM32 |
There was a problem hiding this comment.
codex GPT-6.1-Sol ultra on behalf of Ralf:
This declaration is needed for the build integration: #3173 enables Cython warnings-as-errors, and #2463 originally introduced that setting together with the const DWORD declaration.
I checked Cython 3.2.9 translation with warnings treated as errors. The imported declaration fails with Assignment in pxd file will not be executed. Suggest declaring as const.; the retained declaration passes. This check requires no Windows SDK or native compilation.
The paired changes are the Windows SDK constant declaration and Cython warning policy.
I have retained it here and left this thread open for your review.
aff5d5b to
e165d35
Compare
e165d35 to
494296d
Compare
|
@mdboom I wasn't actually sure myself if this PR is independently mergeable (I explicitly told my agent that's not requirement when building this stack initially), but below is what my agent thinks after analyzing your feedback. I'll work on the "Agree" items first. Please let me know any feedback on the other items. I'll try to work through all bit by bit, based on the information I'll have as I get to each part. codex GPT-6.1-Sol ultra I would address the feedback before merging #3173. It appears safe to land as inactive preparation, but it is not yet a self-contained, validated CUDA 12 integration. I fetched all 11 inline comments, Mike’s review summary, and the conversation. Mike submitted his review with GitHub’s “Changes requested” status. Independent MergeabilityTwo distinctions matter:
I found no dependency on later-layer code that would break existing CUDA 13 functionality. The shared build helper already exists on main; the changes outside CUDA 12 are additive or comments. Mike’s Comments
Direction I RecommendKeep #3173 focused on independently safe preparation:
Version/package selection can remain in #3174 if #3173 explicitly remains inactive preparation. If we want developers to build and use CUDA 12 immediately after merging #3173, its minimum packaging corrections must move forward too. The original stack deliberately allowed intermediate review boundaries that were not fully integrated. Now that we are merging individual layers, tightening this boundary would make the review substantially clearer. |
|
codex GPT-6.1-Sol ultra on behalf of Ralf: The first three agreed follow-ups are pushed, in separate commits:
Full local The remaining stack is restacked and published. Package/version selection and CUDA 12 CI activation remain in their later layers. The runtime-scope and documentation-URL discussions remain open. No full CI run has been triggered for this update. |
|
codex GPT-6.1-Sol ultra on behalf of Ralf: The next scope-reduction pass is pushed:
The stack is restacked and published, and the affected PR descriptions reflect the new boundaries. The new top's complete Git tree is identical to the pre-extraction integrated snapshot: no final source, test, packaging, or CI behavior changed. Full local pre-commit passes on both the narrowed #3173 and the new top. The #3173 build-helper suite passes with 75 passed and 3 skipped. No full CI was triggered. The five relocated-change threads are resolved; the Windows declaration and two documentation-URL discussions remain open. |
|
codex GPT-6.1-Sol ultra on behalf of Ralf: Implemented the agreed documentation policy in dc6166b31297: README, the PyPI description, and build-error guidance consistently use the published CUDA 12.9.7 snapshot. Comments explain why the links are pinned and identify the three files to keep aligned. Direct HTTP checks verified the landing page, overview, installation page, and source-build anchors. Full local pre-commit passes on both #3173 and the final #3182 head, including Lychee. Exact Git tree comparisons confirm that every restacked layer gained only this three-file documentation change. The stack is published and the PR descriptions are updated. Both documentation-URL threads are resolved; the Windows declaration thread remains open for Mike's review. All live PRs remain draft, and no full CI was triggered. |
Signed-off-by: Ralf W. Grosse-Kunstleve <rgrossekunst@nvidia.com>
Signed-off-by: Ralf W. Grosse-Kunstleve <rgrossekunst@nvidia.com>
Signed-off-by: Ralf W. Grosse-Kunstleve <rgrossekunst@nvidia.com>
Signed-off-by: Ralf W. Grosse-Kunstleve <rgrossekunst@nvidia.com>
Signed-off-by: Ralf W. Grosse-Kunstleve <rgrossekunst@nvidia.com>
Signed-off-by: Ralf W. Grosse-Kunstleve <rgrossekunst@nvidia.com>
Signed-off-by: Ralf W. Grosse-Kunstleve <rgrossekunst@nvidia.com>
Signed-off-by: Ralf W. Grosse-Kunstleve <rgrossekunst@nvidia.com>
Signed-off-by: Ralf W. Grosse-Kunstleve <rgrossekunst@nvidia.com>
Signed-off-by: Ralf W. Grosse-Kunstleve <rgrossekunst@nvidia.com>
dc6166b to
2f01e98
Compare
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Summary
Priority: ⬇️ Low Change: Feature Merge Risk: ⚪ Minimal · up to
|
|
|
@mdboom I think I addressed all your feedback, and this PR is now tested with the full CI. Could you please take another look? I cannot set it to auto-merge (apparently that doesn't work for stacks). If it looks good, could you please go ahead and squash-merge this PR as usual? |
Summary
Integrate the imported CUDA 12 sources with the shared build and test tooling, while retaining the CUDA 12 header parser, runtime templates, and legacy modules. This layer carries forward the reviewed source adaptations from #2737; it does not activate CUDA 12 in CI.
bindingspytest marker.latestfollows the current CUDA major.The preceding import remains the exact upstream source snapshot. This diff isolates its integration changes.
Stack / Review Boundary
Layer 2 of 8. Previous: #3172. Next: #3174. All layers and integrated validation.
The eight PRs are review boundaries for one change. #3182 contains the final integrated source state; earlier integrated validation is recorded in #3178. The stack is rebased onto main
dfad7e3658a9. Full hosted CI has not been rerun after this rebase.Suggested Review Order
Validation
At this PR's head, full local
pre-commit run --all-files --show-diff-on-failurepasses, including CUDA 12 checks and Lychee. Direct HTTP checks verified the pinned documentation landing page, overview, installation page, and source-build anchors; the 12.9.8–12.9.10 overview and installation pages return 404. The comments explain the intentional snapshot and identify the copies to keep aligned. No full CI was triggered.Earlier local checks passed the CUDA 12 build-helper suite (75 passed, 3 skipped), validated all 133 generated-file seals across both roots, and rejected simulated seal removal or tampering. A focused Cython 3.2.9 translation check confirms that the Windows
constdeclaration is required when warnings are errors.Earlier integrated-stack validation: 279 focused build tests passed (9 skipped), all 62 sealed CUDA 12 generated files match the imported upstream versions, and shared pytest setup was compared across all three copies. The three capture tests also passed 360 local parallel invocations across 2/4 threads and normal/PTDS stream modes; six path-classification checks cover the shared marker update. Hosted validation passed every CUDA 12 row, including all free-threaded Python targets. Earlier native validation and remaining hosted checks are recorded in #3178; #3182 contains the final source state after this scope split.
Checklist