FailedChanges

Changes from Git (git http://labmaster3.local/git/llvm-project.git)

Summary

  1. [DebugInfo][SelectionDAG] Change order while transferring SDDbgValue to (details)
  2. Make lazyload_metadata.ll resilient to the addition of new metadata (details)
Commit cdd25a4c7410d9af69df4ebe0e640506b8e977b4 by kbessonova
[DebugInfo][SelectionDAG] Change order while transferring SDDbgValue to
another node
SelectionDAG::transferDbgValues() can 'reattach' SDDbgValue from one to
another node, but doesn't change its source order. If the destination
node has the order greater than the SDDbgValue, there are two possible
issues revealed later:
* If debug info is attached to an instruction that is the first
definition of a register, this ends up with a def-after-use and the
debug info gets 'undef' later.
* If MIR has another definition of a register above the debug info, the
debug info may represent a source variable incorrectly because it
appears (significantly) before an instruction corresponded to this debug
info.
So, the patch changes the order of an SDDbgValue when it is moved to a
node with greater order.
Reviewers: dblaikie, jmorse, aprantl
Reviewed By: aprantl
Subscribers: aprantl, hiraditya, llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D71175
The file was addedllvm/test/DebugInfo/X86/sdag-transfer-dbgvalue.ll
The file was modifiedllvm/lib/CodeGen/SelectionDAG/SelectionDAG.cpp
Commit be4704bd41a4dd8bb5c4dd5a614744c69fb3cf8e by david
Make lazyload_metadata.ll resilient to the addition of new metadata
kinds
Summary: The specific number of records loaded depends on the number of
kinds, but the difference between the lazy and not lazy cases does not.
Reviewers: modocache
Subscribers: llvm-commits, dexonsmith, steven_wu, hiraditya, mehdi_amini
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D71882
The file was modifiedllvm/test/ThinLTO/X86/lazyload_metadata.ll