Fix backends load_module name (#4426)
When i try to add new backend to triton, i notice there is no need to
slice name.
If name is "amd" or some name shorter, the module spec will be like:
`ModuleSpec(name='', loader=<_frozen_importlib_external.SourceFileLoader
object at 0x7efb8e129ee0>, origin=...')`, the name will be sliced to be
blank.
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.
- [ ] 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
- [ ] This PR does not need a test because FILL THIS IN.
- 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.)
[AUTOTUNER] Make autotuner take do_bench as a parameter (#4496)
This makes the autotuner device-agnostic. Instead of having to know
about the existence of e.g. do_bench_cudagraph, it can let the callers
decide which backend-specific benchmarking function to use.
See discussion in #4417.
---------
Co-authored-by: Keren Zhou <kerenzhou@openai.com>