llvm-project.git/llvm/test/MachineVerifier, branch users/nico/python-2 Unnamed repository; edit this file 'description' to name the repository. AMDGPU: Add pseudoinstruction for agpr or vgpr constants (#130042) 2025-03-07T02:18:22+00:00 Matt Arsenault Matthew.Arsenault@amd.com 2025-03-07T02:18:22+00:00 7425af4b7aaa31da10bd1bc7996d3bb212c79d88 






[win] NFC: Rename `EHCatchret` to `EHCont` to allow for EH Continuation targets that aren't `catchret` instructions (#129953)
2025-03-06T17:28:44+00:00

Daniel Paoliello
danpao@microsoft.com

2025-03-06T17:28:44+00:00

16e051f0b9ad855e356073c32da6aecfcadf03c8

This change splits out the renaming and comment updates from #129612 as a non-functional change.




This change splits out the renaming and comment updates from #129612 as a non-functional change.






MachineVerifier: Print name of failing subregister index (#129491)
2025-03-04T04:25:34+00:00

Matt Arsenault
Matthew.Arsenault@amd.com

2025-03-04T04:25:34+00:00

4670f0d8275a7eacfba46a17d88d3e2d947f5a61

I'm not sure of a good example to test the "does not fully support"
case.




I'm not sure of a good example to test the "does not fully support"
case.






[AMDGPU] Verify SdwaSel value range (#128898)
2025-02-27T07:11:29+00:00

Frederik Harwath
frederik.harwath@amd.com

2025-02-27T07:11:29+00:00

50b508cc7b2d95f92896df73f49063b5aafec43d

Make the MachineVerifier check that the value provided for an SDWA selection is a
valid value for the SdwaSel enum.




Make the MachineVerifier check that the value provided for an SDWA selection is a
valid value for the SdwaSel enum.






[AMDGPU][NFC] Replace gfx940 and gfx941 with gfx942 in llvm/test (#125711)
2025-02-13T14:17:12+00:00

Fabian Ritter
fabian.ritter@amd.com

2025-02-13T14:17:12+00:00

a33a84ee6348659d7e2483d728a841a9872fe2ec

[AMDGPU][NFC] Replace gfx940 and gfx941 with gfx942 in llvm/test

gfx940 and gfx941 are no longer supported. This is one of a series of PRs to remove them from the code base.

This PR uses gfx942 instead of gfx940 and gfx941 in the test RUN-lines (unless there is already a RUN-line for gfx942).

The only notable difference in the test output is that gfx942 does not force the use of sc0 and sc1 on stores while gfx940 and gfx941 do (cf. https://reviews.llvm.org/D149986).

For SWDEV-512631




[AMDGPU][NFC] Replace gfx940 and gfx941 with gfx942 in llvm/test

gfx940 and gfx941 are no longer supported. This is one of a series of PRs to remove them from the code base.

This PR uses gfx942 instead of gfx940 and gfx941 in the test RUN-lines (unless there is already a RUN-line for gfx942).

The only notable difference in the test output is that gfx942 does not force the use of sc0 and sc1 on stores while gfx940 and gfx941 do (cf. https://reviews.llvm.org/D149986).

For SWDEV-512631






MachineVerifier: Fix check for range type (#124894)
2025-01-30T03:56:12+00:00

Matt Arsenault
Matthew.Arsenault@amd.com

2025-01-30T03:56:12+00:00

60174804611a2543c757d274b293c139412ab41c

We need to permit scalar extending loads with range annotations.

Fix expensive_checks failures after 11db7fb09b36e656a801117d6a2492133e9c2e46




We need to permit scalar extending loads with range annotations.

Fix expensive_checks failures after 11db7fb09b36e656a801117d6a2492133e9c2e46






MachineVerifier: Move test into AMDGPU directory
2025-01-28T14:36:23+00:00

Matt Arsenault
Matthew.Arsenault@amd.com

2025-01-28T14:36:23+00:00

ee1c6a6bc15091155f294d62d0ab67f75a90b7fb

Fixes failures for builds without AMDGPU enabled for test
added in 11db7fb09b36e656a801117d6a2492133e9c2e46





Fixes failures for builds without AMDGPU enabled for test
added in 11db7fb09b36e656a801117d6a2492133e9c2e46







[GlobalISel] Catching inconsistencies in load memory, result, and range metadata type (#121247)
2025-01-28T13:54:34+00:00

Renat Idrisov
4032256+parsifal-47@users.noreply.github.com

2025-01-28T13:54:34+00:00

11db7fb09b36e656a801117d6a2492133e9c2e46

This is a fix for:
https://github.com/llvm/llvm-project/issues/97290
Please let me know if that is the right way to address the issue. Thank
you!

---------

Co-authored-by: Renat Idrisov <parsifal-47@users.noreply.github.com>
Co-authored-by: Matt Arsenault <arsenm2@gmail.com>




This is a fix for:
https://github.com/llvm/llvm-project/issues/97290
Please let me know if that is the right way to address the issue. Thank
you!

---------

Co-authored-by: Renat Idrisov <parsifal-47@users.noreply.github.com>
Co-authored-by: Matt Arsenault <arsenm2@gmail.com>






MachineVerifier: Check stack protector is top-most in frame (#122635)
2025-01-14T14:24:09+00:00

Guy David
49722543+guy-david@users.noreply.github.com

2025-01-14T14:24:09+00:00

da9df6c52a81a29302e45fd77b8dec6b4ae3b5b7

Mitigate against potential bugs that might place it elsewhere and render
the mechanism useless.




Mitigate against potential bugs that might place it elsewhere and render
the mechanism useless.






Revert 86b1b0671cafd "MachineVerifier: Check stack protector is top-most in frame" (#122444)
2025-01-10T12:10:45+00:00

Simon Pilgrim
llvm-dev@redking.me.uk

2025-01-10T12:10:45+00:00

9b49da2b3169544355192dfd8d6909213169d0c1

Reverts llvm/llvm-project#121481

This is causing build failures on EXPENSIVE_CHECKS builds:
https://lab.llvm.org/buildbot/#/builders/187/builds/3653
https://lab.llvm.org/buildbot/#/builders/16/builds/11758




Reverts llvm/llvm-project#121481

This is causing build failures on EXPENSIVE_CHECKS builds:
https://lab.llvm.org/buildbot/#/builders/187/builds/3653
https://lab.llvm.org/buildbot/#/builders/16/builds/11758