Skip to content

Conversation

@anmyachev
Copy link
Contributor

@anmyachev anmyachev commented Oct 31, 2024

This PR change the Triton base from 152ef2d to 78c8054 (Oct 27).
Pass rate: 99.84%

Please do not squash and merge this PR.

Repeating #2595.

anmyachev and others added 4 commits October 24, 2024 22:04
…ly (#4958)

Change to improve platform independence.

How it works?

On Windows:
```python
>>> import sysconfig
>>> sysconfig.get_config_var("EXT_SUFFIX")
'.cp310-win_amd64.pyd'
>>> sysconfig.get_config_var("EXT_SUFFIX").split(".")[-1]
'pyd'
```

On Linux:
```python
>>> import sysconfig
>>> sysconfig.get_config_var("EXT_SUFFIX")
'.cpython-310-x86_64-linux-gnu.so'
>>> sysconfig.get_config_var("EXT_SUFFIX").split(".")[-1]
'so'
```

---------

Signed-off-by: Anatoly Myachev <[email protected]>
Specifically, it fixes problems when `srcLayout` and `dstLayout` have
different number of registers but the same number of not free registers.
We solved the problem by padding free registers to either `srcLayout` or
`dstLayout`, but this can be improved by fixing the `invertAndCompose`
function.
This adds float16 to the list of dtypes tested in
test_tensor_atomic_rmw. Note that the numerics were previously bad for
this test when run in float16; this PR "fixes" the numerics by
internally doing the sum in float32 (upcast, sum, downcast). Since the
purpose is to test the atomic_rmw, and the numerical issues of doing
sums in low-precision dtypes are generally know, I think this strategy
should be fine for this test.
In the case of 16 bit floats operands for tt::AtomicRMWOp, construct
only one LLVM::AtomicRMWOp but use vector of elements.
Such approach allows to generate packed intrinsics and process 2
elements at once.
Added a lit test for f16 vectorized case.
@anmyachev anmyachev marked this pull request as ready for review October 31, 2024 16:09
@anmyachev anmyachev marked this pull request as draft October 31, 2024 16:12
@anmyachev anmyachev marked this pull request as ready for review October 31, 2024 16:23
@anmyachev
Copy link
Contributor Author

@whitneywhtsang @pbchekin Create a merge commit option seems to be disabled for this repository. How do I merge this pull request without squashing?

@pbchekin
Copy link
Contributor

pbchekin commented Nov 1, 2024

@whitneywhtsang @pbchekin Create a merge commit option seems to be disabled for this repository. How do I merge this pull request without squashing?

Yes, usually we enable merge commits temporary for PRs like this.

@anmyachev anmyachev merged commit c5beb57 into main Nov 1, 2024
4 checks passed
@anmyachev anmyachev deleted the amyachev/merge0 branch November 1, 2024 00:39
@whitneywhtsang
Copy link
Contributor

@whitneywhtsang @pbchekin Create a merge commit option seems to be disabled for this repository. How do I merge this pull request without squashing?

We can always use command line to merge instead of UI.

@whitneywhtsang
Copy link
Contributor

FYI @anmyachev, usually I remove the second half of the auto-generated message from like Merge commit '78c8054298a81f578dcd8c79b519981c57dfb665' into amyachev /merge0 to Merge commit '78c8054298a81f578dcd8c79b519981c57dfb665', so we don't mention our personal branch name.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants