llvm-project/llvm/test/Transforms/SafeStack/X86
Adrian Prantl 6825fb64e9 PR32382: Fix emitting complex DWARF expressions.
The DWARF specification knows 3 kinds of non-empty simple location
descriptions:
1. Register location descriptions
  - describe a variable in a register
  - consist of only a DW_OP_reg
2. Memory location descriptions
  - describe the address of a variable
3. Implicit location descriptions
  - describe the value of a variable
  - end with DW_OP_stack_value & friends

The existing DwarfExpression code is pretty much ignorant of these
restrictions. This used to not matter because we only emitted very
short expressions that we happened to get right by accident.  This
patch makes DwarfExpression aware of the rules defined by the DWARF
standard and now chooses the right kind of location description for
each expression being emitted.

This would have been an NFC commit (for the existing testsuite) if not
for the way that clang describes captured block variables. Based on
how the previous code in LLVM emitted locations, DW_OP_deref
operations that should have come at the end of the expression are put
at its beginning. Fixing this means changing the semantics of
DIExpression, so this patch bumps the version number of DIExpression
and implements a bitcode upgrade.

There are two major changes in this patch:

I had to fix the semantics of dbg.declare for describing function
arguments. After this patch a dbg.declare always takes the *address*
of a variable as the first argument, even if the argument is not an
alloca.

When lowering a DBG_VALUE, the decision of whether to emit a register
location description or a memory location description depends on the
MachineLocation — register machine locations may get promoted to
memory locations based on their DIExpression. (Future) optimization
passes that want to salvage implicit debug location for variables may
do so by appending a DW_OP_stack_value. For example:
  DBG_VALUE, [RBP-8]                        --> DW_OP_fbreg -8
  DBG_VALUE, RAX                            --> DW_OP_reg0 +0
  DBG_VALUE, RAX, DIExpression(DW_OP_deref) --> DW_OP_reg0 +0

All testcases that were modified were regenerated from clang. I also
added source-based testcases for each of these to the debuginfo-tests
repository over the last week to make sure that no synchronized bugs
slip in. The debuginfo-tests compile from source and run the debugger.

https://bugs.llvm.org/show_bug.cgi?id=32382
<rdar://problem/31205000>

Differential Revision: https://reviews.llvm.org/D31439

llvm-svn: 300522
2017-04-18 01:21:53 +00:00
..
abi.ll
abi_ssp.ll [Fuchsia] Use thread-pointer ABI slots for stack-protector and safe-stack 2017-02-24 03:10:10 +00:00
addr-taken.ll
array-aligned.ll
array.ll
byval.ll
call.ll Add address space mangling to lifetime intrinsics 2017-04-10 20:18:21 +00:00
cast.ll
coloring-ssp.ll Add address space mangling to lifetime intrinsics 2017-04-10 20:18:21 +00:00
coloring.ll Add address space mangling to lifetime intrinsics 2017-04-10 20:18:21 +00:00
coloring2.ll Add address space mangling to lifetime intrinsics 2017-04-10 20:18:21 +00:00
constant-gep-call.ll
constant-gep.ll
constant-geps.ll
debug-loc-dynamic.ll
debug-loc.ll PR32382: Fix emitting complex DWARF expressions. 2017-04-18 01:21:53 +00:00
debug-loc2.ll Add address space mangling to lifetime intrinsics 2017-04-10 20:18:21 +00:00
dynamic-alloca.ll
escape-addr-pointer.ll
escape-bitcast-store.ll
escape-bitcast-store2.ll
escape-call.ll
escape-casted-pointer.ll
escape-gep-call.ll
escape-gep-invoke.ll
escape-gep-negative.ll
escape-gep-ptrtoint.ll
escape-gep-store.ll
escape-phi-call.ll
escape-select-call.ll
escape-vector.ll
invoke.ll
layout-frag.ll Add address space mangling to lifetime intrinsics 2017-04-10 20:18:21 +00:00
layout-region-split.ll
lit.local.cfg
no-attr.ll
phi-cycle.ll
phi.ll
ret.ll
setjmp.ll
setjmp2.ll
sink-to-use.ll
ssp.ll
store.ll
struct.ll