Happens after splicing#1029
Draft
a-alveyblanc wants to merge 26 commits into
Draft
Conversation
…dependencies-v2
…name into precise deps
a-alveyblanc
marked this pull request as draft
July 21, 2026 22:12
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
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.
Depends on #916. Adds generic machinery to enable transformations to update pre-defined happens-after relations. For example, applying an affine transformation to kernel domains or splitting inames invalidates happens-afters that were defined on the old domain/inames.
Adds:
apply_affine_transform_to_happens_afters: used when inames are transformed but statements in a kernel are not touchedsplice_happens_after_as_consumer: uses existing happens-after information on producers to "splice" in a happens-after relation on a new instruction that is a consumersplice_happens_after_as_producer: same as above, but on the producer sidesplice_happens_after_as_producer_and_consumer: same, but with incoming and outgoing edges. really, just calls the producer and consumer versions in sequence.