Skip to content

Conversation

@jdsteve2
Copy link
Collaborator

@jdsteve2 jdsteve2 commented Apr 26, 2021

THIS PR HAS BEEN REPLACED BY THE FOLLOWING TWO PRs AGAINST MAIN

transformations where loop nest constraints handled:

  • split_iname
  • remove_unused_inames
  • duplicate_inames
  • rename_iname
    • (when new iname doesn't exist)
    • (when new iname DOES exist)
  • (?) tag_inames (currently just erroring if must-nest iname gets tagged as concurrent... anything else need to be done here?
  • join_inames
    • (when within is None)
    • (when within is not None)
  • map_domain

Previous (upstream) PR in chain

…constraints from old branch (https://gitlab.tiker.net/jdsteve2/loopy/iname-sets-in-loop-priorities): UnexpandedInameSet, LoopNestConstraints, process_loop_nest_specification, constrain_loop_nesting, update_must_nest_graph, _expand_iname_sets_in_tuple, check_must_not_nest, check_must_not_nest_against_must_nest_graph
jdsteve2 added 17 commits April 25, 2021 22:09
…om previous branch (https://gitlab.tiker.net/jdsteve2/loopy/iname-sets-in-loop-priorities): check_must_nest(), is_loop_nesting_valid(); rename function is_loop_nesting_valid->loop_nest_constraints_satisfied
@jdsteve2 jdsteve2 changed the title Loop nest constraints v2 Loop nest constraints Apr 26, 2021
jdsteve2 added 22 commits May 8, 2021 23:38
@jdsteve2
Copy link
Collaborator Author

jdsteve2 commented Aug 3, 2021

Closing this PR since it has been replaced by the two PRs linked above. May still be useful to come back and look at this though...

@jdsteve2 jdsteve2 closed this Aug 3, 2021
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.

2 participants