Skip to content
This repository has been archived by the owner on Apr 23, 2021. It is now read-only.

unroll and jam: fix order of jammed bodies #170

Closed
wants to merge 1 commit into from

Conversation

bondhugula
Copy link
Contributor

  • bodies would earlier appear in the order (i, i+3, i+2, i+1) instead of
    (i, i+1, i+2, i+3) for example for factor 4.

  • clean up hardcoded test cases

Signed-off-by: Uday Bondhugula uday@polymagelabs.com

- bodies would earlier appear in the order (i, i+3, i+2, i+1) instead of
  (i, i+1, i+2, i+3) for example for factor 4.

- clean up hardcoded test cases

Signed-off-by: Uday Bondhugula <uday@polymagelabs.com>
tensorflow-copybara pushed a commit to tensorflow/tensorflow that referenced this pull request Oct 9, 2019
- bodies would earlier appear in the order (i, i+3, i+2, i+1) instead of
  (i, i+1, i+2, i+3) for example for factor 4.

- clean up hardcoded test cases

Signed-off-by: Uday Bondhugula <uday@polymagelabs.com>

Closes #170

COPYBARA_INTEGRATE_REVIEW=tensorflow/mlir#170 from bondhugula:ujam b66b405b2b1894a03b376952e32a9d0292042665
PiperOrigin-RevId: 273613131
@bondhugula bondhugula deleted the ujam branch October 10, 2019 18:31
swift-ci pushed a commit to apple/llvm-project that referenced this pull request Dec 24, 2019
- bodies would earlier appear in the order (i, i+3, i+2, i+1) instead of
  (i, i+1, i+2, i+3) for example for factor 4.

- clean up hardcoded test cases

Signed-off-by: Uday Bondhugula <uday@polymagelabs.com>

Closes tensorflow/mlir#170

COPYBARA_INTEGRATE_REVIEW=tensorflow/mlir#170 from bondhugula:ujam b66b405b2b1894a03b376952e32a9d0292042665
PiperOrigin-RevId: 273613131
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants