Skip to content

Conversation

@Lunderberg
Copy link
Contributor

In SchedulePostProcToPrimfunc, when the axis separator attribute is moved to the buffer properties, it doesn't update buffers that are in the buffer bind scope. This occurs if Stage.tensorize is called for a stage whose layout transformation includes te.AXIS_SEPARATOR.

In SchedulePostProcToPrimfunc, when the axis separator attribute is
moved to the buffer properties, it doesn't update buffers that are in
the buffer bind scope.  This occurs if `Stage.tensorize` is called for
a stage whose layout transformation includes `te.AXIS_SEPARATOR`.
@Lunderberg Lunderberg force-pushed the buffer_bind_axis_separator branch from be9ae02 to d618b96 Compare March 30, 2022 14:04
@Lunderberg
Copy link
Contributor Author

One failing unit test, due to HTTP error. Bumping CI to restart.

@masahi masahi merged commit b5cad84 into apache:main Mar 30, 2022
@Lunderberg Lunderberg deleted the buffer_bind_axis_separator branch March 30, 2022 20:40
pfk-beta pushed a commit to pfk-beta/tvm that referenced this pull request Apr 11, 2022
In SchedulePostProcToPrimfunc, when the axis separator attribute is
moved to the buffer properties, it doesn't update buffers that are in
the buffer bind scope.  This occurs if `Stage.tensorize` is called for
a stage whose layout transformation includes `te.AXIS_SEPARATOR`.
mehrdadh pushed a commit to mehrdadh/tvm that referenced this pull request Apr 11, 2022
In SchedulePostProcToPrimfunc, when the axis separator attribute is
moved to the buffer properties, it doesn't update buffers that are in
the buffer bind scope.  This occurs if `Stage.tensorize` is called for
a stage whose layout transformation includes `te.AXIS_SEPARATOR`.
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