Today we merged the PR https://github.com/apache/tvm/pull/9727 which added layout transform as a TE schedule primitive. The PR also includes a change in how buffers are loaded / stored, resulting in the massive change throughout the codebase. If you are working on something that touches TIR, you probably need to rebase and resolve conflicts.
Ideally, we would break the PR into smaller ones and land each of them step-by-step. But due to various reasons, we decided to land the PR wholesale. More details and follow-up actions are described in https://github.com/apache/tvm/issues/10505.
In principle, we do not expect perf regression from this PR. But since the PR added many modifications to the TIR -> ... -> TIR -> codegen pipeline, I wouldn’t be surprised if the lowered output becomes different after this PR. Please report any regression you encounter here.
@masahi: It really caught us by surprise . Is there a way to place announcements like this (with the potential of causing additional workload) in a more prominent place?
Ok @MJKlaiber, I think I “pinned” this topic globally, so whenever you visit https://discuss.tvm.apache.org/ you will see this announcement kept at the top. Is this “visible enough”? Or do you also want to see a pinned issue on github?
@wrongtest one way to quickly work around this issue is to use an intrinsic to represent predicated Load/Store. Alternatively, as @vinx13 mentioned, we might want to bring the predicate back somehow, but it might require a short RFC
.
. Is there a way to place announcements like this (with the potential of causing additional workload) in a more prominent place?