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


  1. [NFC] Tidy-ups to TimeProfiler.cpp (details)
  2. Mark some tests as xfail on AArch64 Linux (details)
  3. [LiveDebugValues] Introduce entry values of unmodified params (details)
  4. ImplicitNullChecks: Don't add a dead definition of DepMI as live-in (details)
Commit df943a7a08102ed3d1f632e88b24a024a7c4ba81 by russell.gallop
[NFC] Tidy-ups to TimeProfiler.cpp
Remove unused include Make fields const where possible Move
initialisation to initialiser list
Differential Revision:
The file was modifiedllvm/lib/Support/TimeProfiler.cpp
Commit 6d18e5366c9a0bffe45b179a830483b3f2ec9fa9 by diana.picus
Mark some tests as xfail on AArch64 Linux
I have either opened new bug reports for these tests, or added links to
existing bugs.
This should help make the lldb-aarch64-ubuntu buildbot green (there will
still be some unexpected passes that someone should look into, but those
can be handled later).
The file was modifiedlldb/packages/Python/lldbsuite/test/functionalities/breakpoint/require_hw_breakpoints/
The file was modifiedlldb/packages/Python/lldbsuite/test/lang/cpp/trivial_abi/
The file was modifiedlldb/packages/Python/lldbsuite/test/functionalities/step-avoids-no-debug/
The file was modifiedlldb/packages/Python/lldbsuite/test/commands/expression/static-initializers/
The file was modifiedlldb/packages/Python/lldbsuite/test/functionalities/return-value/
The file was modifiedlldb/packages/Python/lldbsuite/test/linux/builtin_trap/
The file was modifiedlldb/packages/Python/lldbsuite/test/functionalities/show_location/
The file was modifiedlldb/packages/Python/lldbsuite/test/functionalities/tail_call_frames/thread_step_out_or_return/
The file was modifiedlldb/packages/Python/lldbsuite/test/functionalities/load_unload/
The file was modifiedlldb/packages/Python/lldbsuite/test/functionalities/inline-stepping/
Commit 4cfceb910692f9e894622da1b394324503667e46 by djordje.todorovic
[LiveDebugValues] Introduce entry values of unmodified params
The idea is to remove front-end analysis for the parameter's value
modification and leave it to the value tracking system. Front-end in
some cases marks a parameter as modified even the line of code that
modifies the parameter gets optimized, that implies that this will cover
more entry values even. In addition, extending the support for modified
parameters will be easier with this approach.
Since the goal is to recognize if a parameter’s value has changed, the
idea at very high level is: If we encounter a DBG_VALUE other than the
entry value one describing the same variable (parameter), we can assume
that the variable’s value has changed and we should not track its entry
value any more. That would be ideal scenario, but due to various LLVM
optimizations, a variable’s value could be just moved around from one
register to another
(and there will be additional DBG_VALUEs describing the same variable),
so we have to recognize such situation (otherwise, we will lose a lot of
entry values) and salvage the debug entry value.
Differential Revision:
The file was modifiedlldb/packages/Python/lldbsuite/test/functionalities/param_entry_vals/basic_entry_values_x86_64/main.cpp
The file was addedllvm/test/DebugInfo/MIR/X86/entry-value-of-modified-param.mir
The file was modifiedllvm/lib/CodeGen/LiveDebugValues.cpp
The file was modifiedllvm/test/DebugInfo/MIR/ARM/dbgcall-site-propagated-value.mir
The file was modifiedlldb/packages/Python/lldbsuite/test/functionalities/param_entry_vals/basic_entry_values_x86_64/
The file was addedllvm/test/DebugInfo/MIR/X86/propagate-entry-value-cross-bbs.mir
The file was addedllvm/test/DebugInfo/MIR/X86/kill-entry-value-after-diamond-bbs.mir
The file was addedllvm/test/DebugInfo/MIR/X86/entry-values-diamond-bbs.mir
Commit f8c0cfc24eab0f23e3ebc65b10ee4276b1f15eeb by paulsson
ImplicitNullChecks: Don't add a dead definition of DepMI as live-in
This is one of the fixes needed to reapply D68267 which improves
verification of live-in lists.
Review: craig.topper
The file was modifiedllvm/lib/CodeGen/ImplicitNullChecks.cpp
The file was modifiedllvm/test/CodeGen/X86/implicit-null-checks.mir