You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix hardcoding of shared address space in target independent code (#4833)
Currently, we hardcode the address space of shared memory in target
independent code. This wouldn't work for a backend that uses a different
address space for shared memory, so this PR does two things:
1. Removes unnecessary casts (that go from a shared memory ptr to a
shared memory ptr) and instances of hardcoding that can be avoided. It
does these cleanups only to target independent code - if needed, I can
do it to the backends as well
2. Introduces getSharedAddressSpace to TargetInfo and uses it for the
rest
The core Triton is a small number of people, and we receive many PRs
(thank
you!). To help us review your code more quickly, **if you are a new
contributor (less than 3 PRs merged) we ask that you complete the
following
tasks and include the filled-out checklist in your PR description.**
Complete the following tasks before sending your PR, and replace `[ ]`
with
`[x]` to indicate you have done them.
- [x] I am not making a trivial change, such as fixing a typo in a
comment.
- [x] I have written a PR description following these
[rules](https://cbea.ms/git-commit/#why-not-how).
- [x] I have run `pre-commit run --from-ref origin/main --to-ref HEAD`.
- Select one of the following.
- [ ] I have added tests.
- `/test` for `lit` tests
- `/unittest` for C++ tests
- `/python/test` for end-to-end tests
- [x] This PR does not need a test because it is a non-functional change
and any existing tests that exercise shared memory should exercise the
changes in this test.
- Select one of the following.
- [X] I have not added any `lit` tests.
- [ ] The `lit` tests I have added follow these [best
practices](https://mlir.llvm.org/getting_started/TestingGuide/#filecheck-best-practices),
including the "tests should be minimal" section. (Usually running Python
code
and using the instructions it generates is not minimal.)
0 commit comments