en Copyright 2015 Java http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/MIR/X86/livedebugvalues_loop_within_loop.mir#d391e4fe [X86] Update RET/LRET instruction to use the same naming convention as IRET (PR36876). NFCBe more consistent in the naming convention for the various RET instructions to specify in terms of bitwidth.Helps prevent future scheduler model mismatches like those that were only addressed in D44687.Differential Revision: https://reviews.llvm.org/D113302 List of files: /llvm-project-15.0.7/llvm/test/DebugInfo/MIR/X86/livedebugvalues_loop_within_loop.mir Sun, 07 Nov 2021 15:06:54 +0000 Simon Pilgrim <llvm-dev@redking.me.uk> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/MIR/X86/livedebugvalues_loop_within_loop.mir#0caeaff1 [LiveDebugValues][NFC] Re-land 60db26a66d, add instr-ref testsThis was landed but reverted in 5b9c2b1bea7 due to asan picking up a memoryleak. This is fixed in the change to InstrRefBasedImpl.cpp. Originalcommit message follows:[LiveDebugValues][NFC] Add instr-ref tests, adapt old testsThis patch adds a few tests in DebugInfo/MIR/InstrRef/ of interestingbehaviour that the instruction referencing implementation ofLiveDebugValues has. Mostly, these tests exist to ensure that if yougive the "-experimental-debug-variable-locations" command line switch,the right implementation runs; and to ensure it behaves the same way asthe VarLoc LiveDebugValues implementation.I've also touched roughly 30 other tests, purely to make the tests lessrigid about what output to accept. DBG_VALUE instructions are usuallyprinted with a trailing !debug-location indicating its scope: !debug-location !1234However InstrRefBasedLDV produces new DebugLoc instances on the fly,meaning there sometimes isn't a numbered node when they're printed,making the output: !debug-location !DILocation(line: 0, blah blah)Which causes a ton of these tests to fail. This patch removes checks forthat final part of each DBG_VALUE instruction. None of them appear tobe actually checking the scope is correct, just that it's present, soI don't believe there's any loss in coverage here.Differential Revision: https://reviews.llvm.org/D83054 List of files: /llvm-project-15.0.7/llvm/test/DebugInfo/MIR/X86/livedebugvalues_loop_within_loop.mir Fri, 11 Sep 2020 11:10:55 +0000 Jeremy Morse <jeremy.morse@sony.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/MIR/X86/livedebugvalues_loop_within_loop.mir#5b9c2b1b Revert "[LiveDebugValues][NFC] Add instr-ref tests, adapt old tests"Asan has picked up a memory leak, which will require some investigation:http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-fast/builds/45372/steps/check-llvm%20asan/logs/stdioThis reverts commit 60db26a66d5346b2feae279f6c928bde48078893. List of files: /llvm-project-15.0.7/llvm/test/DebugInfo/MIR/X86/livedebugvalues_loop_within_loop.mir Wed, 26 Aug 2020 16:19:13 +0000 Jeremy Morse <jeremy.morse@sony.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/MIR/X86/livedebugvalues_loop_within_loop.mir#60db26a6 [LiveDebugValues][NFC] Add instr-ref tests, adapt old testsThis patch adds a few tests in DebugInfo/MIR/InstrRef/ of interestingbehaviour that the instruction referencing implementation ofLiveDebugValues has. Mostly, these tests exist to ensure that if yougive the "-experimental-debug-variable-locations" command line switch,the right implementation runs; and to ensure it behaves the same way asthe VarLoc LiveDebugValues implementation.I've also touched roughly 30 other tests, purely to make the tests lessrigid about what output to accept. DBG_VALUE instructions are usuallyprinted with a trailing !debug-location indicating its scope: !debug-location !1234However InstrRefBasedLDV produces new DebugLoc instances on the fly,meaning there sometimes isn't a numbered node when they're printed,making the output: !debug-location !DILocation(line: 0, blah blah)Which causes a ton of these tests to fail. This patch removes checks forthat final part of each DBG_VALUE instruction. None of them appear tobe actually checking the scope is correct, just that it's present, soI don't believe there's any loss in coverage here.Differential Revision: https://reviews.llvm.org/D83054 List of files: /llvm-project-15.0.7/llvm/test/DebugInfo/MIR/X86/livedebugvalues_loop_within_loop.mir Tue, 25 Aug 2020 15:43:47 +0000 Jeremy Morse <jeremy.morse@sony.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/MIR/X86/livedebugvalues_loop_within_loop.mir#e7b2d9f4 [DBG][LIVEDEBUGVALUES][NFC] Add Targeted LiveDebugValues Behaviour Tests.Adds 22 distinct tests that exercise the live-debug-values passesexpected behaviour.reviewers: aprantl, vskDifferential revision: https://reviews.llvm.org/D72515 List of files: /llvm-project-15.0.7/llvm/test/DebugInfo/MIR/X86/livedebugvalues_loop_within_loop.mir Tue, 14 Jan 2020 15:51:11 +0000 Tom Weaver <Tom.Weaver@Sony.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/MIR/X86/livedebugvalues_loop_within_loop.mir#35787e3a [DBG][LIVEDEBUGVALUES][NFC] Add Targeted LiveDebugValues Behaviour Tests.Adds 22 distinct tests that exercise the live-debug-values passesexpected behaviour.reviewers: aprantl, vskDifferential revision: https://reviews.llvm.org/D72515 List of files: /llvm-project-15.0.7/llvm/test/DebugInfo/MIR/X86/livedebugvalues_loop_within_loop.mir Tue, 14 Jan 2020 14:43:30 +0000 Tom Weaver <Tom.Weaver@Sony.com>