These tests weren't checking anything and would pass even after swapping
the correct call_intrinsic to XXX_BROKEN, noticed this while working on
#9628
<!---
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.
-->
# New contributor declaration
- [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 `Fixing existing tests`.
- 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.)

)
These tests weren't checking anything and would pass even after swapping
the correct call_intrinsic to XXX_BROKEN, noticed this while working on
triton-lang#9628
<!---
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.
-->
# New contributor declaration
- [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 `Fixing existing tests`.
- 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.)

[gfx906 has](https://llvm.org/docs/AMDGPU/AMDGPUAsmGFX906.html)
v_dot2_f32_f16 and v_dot4_i32_i8 via VOP3P but no MFMA. Nearly the same
dot intrinsics as
[gfx908](https://llvm.org/docs/AMDGPU/AMDGPUAsmGFX908.html); LLVM
transparently selects correct form based on HasDot1Insts/HasDot2Insts
feature bits.
New ISAFamily::GCN5_1 enum mapped from GK_GFX906 with wave64, DPP
broadcast, and supportsVDot; this is GCN so not marked as RDNA/CDNA and
most gates don't need updated.
warpReduce refactored from isCDNA/isRDNA negative enumeration to a
`getIsaVersion()` check (gfx90a+ || gfx11+).

)
These tests weren't checking anything and would pass even after swapping
the correct call_intrinsic to XXX_BROKEN, noticed this while working on
triton-lang#9628
<!---
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.
-->
# New contributor declaration
- [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 `Fixing existing tests`.
- 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.)

[gfx906 has](https://llvm.org/docs/AMDGPU/AMDGPUAsmGFX906.html)
v_dot2_f32_f16 and v_dot4_i32_i8 via VOP3P but no MFMA. Nearly the same
dot intrinsics as
[gfx908](https://llvm.org/docs/AMDGPU/AMDGPUAsmGFX908.html); LLVM
transparently selects correct form based on HasDot1Insts/HasDot2Insts
feature bits.
New ISAFamily::GCN5_1 enum mapped from GK_GFX906 with wave64, DPP
broadcast, and supportsVDot; this is GCN so not marked as RDNA/CDNA and
most gates don't need updated.
warpReduce refactored from isCDNA/isRDNA negative enumeration to a
`getIsaVersion()` check (gfx90a+ || gfx11+).

)
These tests weren't checking anything and would pass even after swapping
the correct call_intrinsic to XXX_BROKEN, noticed this while working on
triton-lang#9628
<!---
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.
-->
# New contributor declaration
- [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 `Fixing existing tests`.
- 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.)

[gfx906 has](https://llvm.org/docs/AMDGPU/AMDGPUAsmGFX906.html)
v_dot2_f32_f16 and v_dot4_i32_i8 via VOP3P but no MFMA. Nearly the same
dot intrinsics as
[gfx908](https://llvm.org/docs/AMDGPU/AMDGPUAsmGFX908.html); LLVM
transparently selects correct form based on HasDot1Insts/HasDot2Insts
feature bits.
New ISAFamily::GCN5_1 enum mapped from GK_GFX906 with wave64, DPP
broadcast, and supportsVDot; this is GCN so not marked as RDNA/CDNA and
most gates don't need updated.
warpReduce refactored from isCDNA/isRDNA negative enumeration to a
`getIsaVersion()` check (gfx90a+ || gfx11+).

)
These tests weren't checking anything and would pass even after swapping
the correct call_intrinsic to XXX_BROKEN, noticed this while working on
triton-lang#9628
<!---
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.
-->
# New contributor declaration
- [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 `Fixing existing tests`.
- 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.)

[gfx906 has](https://llvm.org/docs/AMDGPU/AMDGPUAsmGFX906.html)
v_dot2_f32_f16 and v_dot4_i32_i8 via VOP3P but no MFMA. Nearly the same
dot intrinsics as
[gfx908](https://llvm.org/docs/AMDGPU/AMDGPUAsmGFX908.html); LLVM
transparently selects correct form based on HasDot1Insts/HasDot2Insts
feature bits.
New ISAFamily::GCN5_1 enum mapped from GK_GFX906 with wave64, DPP
broadcast, and supportsVDot; this is GCN so not marked as RDNA/CDNA and
most gates don't need updated.
warpReduce refactored from isCDNA/isRDNA negative enumeration to a
`getIsaVersion()` check (gfx90a+ || gfx11+).