-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
[Pipeliner] Handle masking for atomic_rmw #5231
base: main
Are you sure you want to change the base?
Conversation
82b559f
to
d59dd74
Compare
|
||
// Check that the stream pipeliner updates atomic op in the k-loop correctly | ||
// CHECK-LABEL: _triton_gemm_kernel_atomic_rmw | ||
// CHECK: tt.atomic_rmw fadd, acq_rel, gpu |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you also insert CHECK:
lines for the loop structure scf.for
and scf.yield
to be clear? Like L36 - L42.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for the comments, added.
d59dd74
to
a50c820
Compare
@zhanglx13, could you please help trigger a CI build and then merge this PR? Thanks |
This PR is to support atomic_rmw in the function
predicateOp
to mask operations during scheduling.New contributor declaration
I am not making a trivial change, such as fixing a typo in a comment.
I have written a PR description following these
rules.
I have run
pre-commit run --from-ref origin/main --to-ref HEAD
.Select one of the following.
/test
forlit
tests/unittest
for C++ tests/python/test
for end-to-end testsFILL THIS IN
.Select one of the following.
lit
tests.lit
tests I have added follow these best practices,including the "tests should be minimal" section. (Usually running Python code
and using the instructions it generates is not minimal.)