[llvm] [GlobalISel] Catching inconsistencies in load memory, result, and range metadata type (PR #121247)
Matt Arsenault via llvm-commits
llvm-commits at lists.llvm.org
Mon Jan 6 08:31:53 PST 2025
================
@@ -1274,6 +1274,12 @@ void MachineVerifier::verifyPreISelGenericInstruction(const MachineInstr *MI) {
if (TypeSize::isKnownGT(MMO.getSize().getValue(),
ValTy.getSizeInBytes()))
report("load memory size cannot exceed result size", MI);
+
+ if (MMO.getRanges() && (ValTy.isVector() != MMO.getType().isVector())) {
----------------
arsenm wrote:
This set of IR tests happens to only use 64-bit values
> , it breaks existing tests.
It's possible there are broken tests or bugs, that's why we write these verifiers
https://github.com/llvm/llvm-project/pull/121247
More information about the llvm-commits
mailing list