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.

Sign up for GitHub

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

Jump to bottom

[Tracking Issue] Formalize the semantics of partial updates #78

Open
yzh119 opened this issue Dec 11, 2022 · 0 comments
Open

[Tracking Issue] Formalize the semantics of partial updates #78

yzh119 opened this issue Dec 11, 2022 · 0 comments

Comments

@yzh119
Copy link
Member

yzh119 commented Dec 11, 2022 •
edited

Motivation

After format decomposition, many of the generated sparse iterations (or blocks after lowering) only perform partial updates: only some blocks need to initialize the output buffer with zeros.

Currently, SparseTIR does not have language constructs to describe the partial update semantics.

Solution

TBD
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@yzh119