Skip to content

Conversation

@Lunderberg
Copy link
Contributor

@Lunderberg Lunderberg commented Sep 16, 2022

Follow-up from #11269, which allowed schedule arguments of the buffer to be transformed to be specified as a string, or as a tir::Buffer. The string handling worked correctly, but the tir::Buffer object was handled incorrectly. This commit corrects the handling of tir::Buffer arguments when scheduling, and adds a unit test to validate this behavior.

cc @Hzfengsy @junrushao1994

Follow-up from apache#11269, which allowed
schedule arguments of the buffer to be transformed to be specified as
a string, or as a `tir::Buffer`.  The string handling worked
correctly, but the `tir::Buffer` object was handled incorrectly.  This
commit corrects the handling of `tir::Buffer` arguments when
scheduling, and adds a unit test to validate this behavior.
@vinx13 vinx13 merged commit 79c48f3 into apache:main Sep 19, 2022
@Lunderberg Lunderberg deleted the tir_schedule_buffer_arg branch September 19, 2022 19:06
xinetzone pushed a commit to daobook/tvm that referenced this pull request Nov 25, 2022
…ache#12816)

Follow-up from apache#11269, which allowed
schedule arguments of the buffer to be transformed to be specified as
a string, or as a `tir::Buffer`.  The string handling worked
correctly, but the `tir::Buffer` object was handled incorrectly.  This
commit corrects the handling of `tir::Buffer` arguments when
scheduling, and adds a unit test to validate this behavior.
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