-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Relay]Frontend][Onnx] Remove pop that interferes with nested loops. #7781
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Looks like the assertion that you modified is breaking CI: https://ci.tlcpack.ai/blue/organizations/jenkins/tvm/detail/PR-7781/1/pipeline @jwfromm |
@tmoreau89 yeah that new assert actually triggers for inner nested loops. I've changed it to only check in the outermost scope of the model which should be the sweet spot. |
Thank you @jwfromm @mbrookhart the PR has been merged. |
…pache#7781) * Remove popping that interferes with nested loops. * Only check user inputs in the outer-most graph scope. * Fix style. Co-authored-by: Ubuntu <jwfromm@jwfromm-cpu-dev.itxhlkosmouevgkdrmwxfbs5qh.xx.internal.cloudapp.net>
…pache#7781) * Remove popping that interferes with nested loops. * Only check user inputs in the outer-most graph scope. * Fix style. Co-authored-by: Ubuntu <jwfromm@jwfromm-cpu-dev.itxhlkosmouevgkdrmwxfbs5qh.xx.internal.cloudapp.net>
…pache#7781) * Remove popping that interferes with nested loops. * Only check user inputs in the outer-most graph scope. * Fix style. Co-authored-by: Ubuntu <jwfromm@jwfromm-cpu-dev.itxhlkosmouevgkdrmwxfbs5qh.xx.internal.cloudapp.net>
…pache#7781) * Remove popping that interferes with nested loops. * Only check user inputs in the outer-most graph scope. * Fix style. Co-authored-by: Ubuntu <jwfromm@jwfromm-cpu-dev.itxhlkosmouevgkdrmwxfbs5qh.xx.internal.cloudapp.net>
PR #7699 introduced a check for user provided shapes that arent found in the input graph. My implementation used
pop
, which it turns out can cause issues in nested loops. Unfortunately, its difficult to write a test case that triggers this error, but we should avoid pop in general. This PR replaces the pop based approach with a much safer way to check the same condition.