Skip to content

Conversation

@Lunderberg
Copy link
Contributor

@Lunderberg Lunderberg commented Sep 16, 2022

Follow-up from #11970, to improve performance. In the initial implementation, the analyzer->int_set would compute the intersection of all scope-based constraints when entering the scope, even if they weren't actually used. This commit delays the call to Intersect until required, following the same behavior as ConstIntBound.

cc @Hzfengsy @junrushao1994

Follow-up from apache#11970, to improve
performance.  In the initial implementation, the `analyzer->int_set`
would compute the intersection of all scope-based constraints when
entering the scope, even if they weren't actually used.  This commit
delays the call to `Intersect` until required, following the same
behavior as `ConstIntBound`.
@wrongtest-intellif
Copy link
Contributor

Also happy to know IRVisitorWithAnalyzer now come back to life! I remember it is in somewhat broken state for a long time.

Copy link
Contributor

@tkonolige tkonolige left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @Lunderberg!

@tkonolige tkonolige merged commit e30ac71 into apache:main Sep 19, 2022
@Lunderberg Lunderberg deleted the int_set_analyzer_lazy_eval branch September 19, 2022 19:06
xinetzone pushed a commit to daobook/tvm that referenced this pull request Nov 25, 2022
…pache#12821)

Follow-up from apache#11970, to improve
performance.  In the initial implementation, the `analyzer->int_set`
would compute the intersection of all scope-based constraints when
entering the scope, even if they weren't actually used.  This commit
delays the call to `Intersect` until required, following the same
behavior as `ConstIntBound`.
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.

3 participants