This is to avoid generating duplicate llvm.dbg.value instrinsic if it already exists after the Instruction.
Summary: Before inserting llvm.dbg.value instruction, LLVM checks if the same instruction is already present before the instruction to avoid duplicates.
Currently it misses to check if it already exists after the instruction.
flang generates IR like this.
%4 = load i32, i32* %i1_311, align 4, !dbg !42 call void @llvm.dbg.value(metadata i32 %4, metadata !35, metadata !DIExpression()), !dbg !33
When this IR is processed in llvm, it ends up inserting duplicates.
%4 = load i32, i32* %i1_311, align 4, !dbg !42 call void @llvm.dbg.value(metadata i32 %4, metadata !35, metadata !DIExpression()), !dbg !33 call void @llvm.dbg.value(metadata i32 %4, metadata !35, metadata !DIExpression()), !dbg !33
We have now updated LdStHasDebugValue to include the cases when instruction is already
followed by same dbg.value instruction we intend to insert.
Now,
- Definition and usage of function LdStHasDebugValue are deleted.
- RemoveRedundantDbgInstrs is called for the cleanup of duplicate dbg.value's
Testing:
- Added unit test for validation
- check-llvm
- check-debuginfo (the debug info integration tests)
isDbgValueMatches reads a bit awkward to me. Perhaps isDbgValueMatching?