Skip to content
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

[TIR] Fix the thread binding iter_var dtype in Bind primitive #16074

Merged
merged 1 commit into from Nov 5, 2023

Conversation

Hzfengsy
Copy link
Member

@Hzfengsy Hzfengsy commented Nov 5, 2023

As a follow up PR of #16041, this PR fixes the iter_var dtype generated by the schedule primitive bind. Now the iter_var dtype is the same as the loop_var.

Note that this PR changes the internal interface (tir interface) of the bind primitive. But it does not change the user interface (python side, and concrete_schedule.cc side).

cc @junrushao

@Hzfengsy Hzfengsy marked this pull request as ready for review November 5, 2023 07:45
As a follow up PR of apache#16041, this PR fixes the iter_var dtype generated
by the schedule primitive `bind`. Now the iter_var dtype is the same as
the loop_var.

Note that this PR changes the internal interface (tir interface) of the
bind primitive. But it does not change the user interface (python side,
and concrete_schedule.cc side).
@junrushao junrushao merged commit 1de5aa5 into apache:main Nov 5, 2023
17 checks passed
@Hzfengsy Hzfengsy deleted the fix_bind_iter_var_dtype branch November 7, 2023 01:52
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.

None yet

2 participants