mcpp:plugins 0.2.0 - #356
Merged
Merged
Conversation
Two new members and a route that had no payload behind it. `mcpp.rules.sycl` (feature `rules-sycl`) drives the `xim:dpcpp` payload over `.sycl` translation units, which mcpp 2026.9.6.1 classifies as device sources. `mcpp.rules.hip` (feature `rules-hip`) compiles `.hip` units on the NVIDIA platform, where HIP is a header layer over the CUDA runtime and the compiler is the project's own clang. And `mcpp.rules.spirv` now drives glslc as well as glslang, because `xim:shaderc` publishes one -- the route that rule's own source used to call "a claim rather than a feature". The floor recorded here is 2026.9.6.1, the highest among the members rather than any one feature's, and the descriptor says so: a project on 2026.9.5.4 that wants only `rules-cuda` is refused by it. Splitting the package per member is the alternative and is not taken, because one host-module package is what makes the collection a collection. One sha256 for both URLs, verified by downloading each: the GitHub archive of the tag and the GitCode asset are byte for byte the same 47,792 bytes. 0.1.1 and 0.1.0 stay, so a consumer already pinning either keeps resolving.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two new members and a route that had no payload behind it.
mcpp.rules.sycl(featurerules-sycl) drives thexim:dpcpppayload over.sycltranslation units, which mcpp 2026.9.6.1 classifies as device sources.mcpp.rules.hip(featurerules-hip) compiles.hipunits on the NVIDIAplatform, where HIP is a header layer over the CUDA runtime and the compiler is
the project's own clang. And
mcpp.rules.spirvnow drives glslc as well asglslang, because
xim:shadercpublishes one -- the route that rule's ownsource used to call "a claim rather than a feature".
The floor recorded here is 2026.9.6.1, the highest among the members rather
than any one feature's, and the descriptor says so: a project on 2026.9.5.4
that wants only
rules-cudais refused by it. Splitting the package per memberis the alternative and is not taken, because one host-module package is what
makes the collection a collection.
One sha256 for both URLs, verified by downloading each: the GitHub archive of
the tag and the GitCode asset are byte for byte the same 47,792 bytes.
0.1.1 and 0.1.0 stay, so a consumer already pinning either keeps resolving.