mirror of
https://github.com/RPCS3/llvm-mirror.git
synced 2024-10-20 19:42:54 +02:00
927308d763
I originally reapplied this in 257550, but had to revert again due to bot
breakage. The only change in this version is to allow either the TypeSize
or the TypeAllocSize of the variable to be the one represented in debug info
(hopefully in the future we can figure out how to encode the difference).
Additionally, several bot failures following r257550, were due to
optimizer bugs now fixed in r257787 and r257795.
r257550 commit message was:
```
The follow extra changes were made to test cases:
Manually making the variable be the actual type instead of a pointer
to avoid pointer-size differences in generic code:
LLVM :: DebugInfo/Generic/2010-03-24-MemberFn.ll
LLVM :: DebugInfo/Generic/2010-04-06-NestedFnDbgInfo.ll
LLVM :: DebugInfo/Generic/2010-05-03-DisableFramePtr.ll
LLVM :: DebugInfo/Generic/varargs.ll
Delete sizing information from debug info for the same reason
(but the presence of the pointer was important to the test case):
LLVM :: DebugInfo/Generic/restrict.ll
LLVM :: DebugInfo/Generic/tu-composite.ll
LLVM :: Linker/type-unique-type-array-a.ll
LLVM :: Linker/type-unique-simple2.ll
Fixing an incorrect DW_OP_deref
LLVM :: DebugInfo/Generic/2010-05-03-OriginDIE.ll
Fixing a missing DW_OP_deref
LLVM :: DebugInfo/Generic/incorrect-variable-debugloc.ll
Additionally, clang should no longer complain during bootstrap should no
longer happen after r257534.
The original commit message was:
``
Summary:
Teach the Verifier to make sure that the storage size given to llvm.dbg.declare
or the value size given to llvm.dbg.value agree with what is declared in
DebugInfo. This is implicitly assumed in a number of passes (e.g. in SROA).
Additionally this catches a number of common mistakes, such as passing a
pointer when a value was intended or vice versa.
One complication comes from stack coloring which modifies the original IR when
it merges allocas in order to make sure that if AA falls back to the IR it gets
the correct result. However, given this new invariant, indiscriminately
replacing one alloca by a different (differently sized one) is no longer valid.
Fix this by just undefing out any use of the alloca in a dbg.declare in this
case.
Additionally, I had to fix a number of test cases. Of particular note:
- I regenerated dbg-changes-codegen-branch-folding.ll from the given source as
it was affected by the bug fixed in r256077
- two-cus-from-same-file.ll was changed to avoid having a variable-typed debug
variable as that would depend on the target, even though this test is
supposed to be generic
- I had to manually declared size/align for reference type. See also the
discussion for D14275/r253186.
- fpstack-debuginstr-kill.ll required changing `double` to `long double`
- most others were just a question of adding OP_deref
``
```
llvm-svn: 257850
|
||
|---|---|---|
| .. | ||
| AArch64 | ||
| ARM | ||
| COFF | ||
| Generic | ||
| Inputs | ||
| Mips | ||
| MIR | ||
| PDB | ||
| PowerPC | ||
| Sparc | ||
| SystemZ | ||
| X86 | ||
| arm-relocs.test | ||
| debuglineinfo-macho.test | ||
| debuglineinfo.test | ||
| debugmacinfo.test | ||
| dwarfdump-64-bit-dwarf.test | ||
| dwarfdump-accel.test | ||
| dwarfdump-debug-frame-simple.test | ||
| dwarfdump-debug-loc-simple.test | ||
| dwarfdump-dump-flags.test | ||
| dwarfdump-dwp.test | ||
| dwarfdump-invalid.test | ||
| dwarfdump-line-dwo.test | ||
| dwarfdump-macho-relocs.test | ||
| dwarfdump-macho-universal.test | ||
| dwarfdump-objc.test | ||
| dwarfdump-pubnames.test | ||
| dwarfdump-ranges.test | ||
| dwarfdump-type-units.test | ||
| dwarfdump-zlib.test | ||
| dwo.ll | ||
| llvm-symbolizer-zlib.test | ||
| llvm-symbolizer.test | ||
| member-pointers.o | ||
| missing-abstract-variable.o | ||
| skeletoncu.ll | ||