Bjorn Pettersson 8b01057380 [DebugInfo] Check size of variable in ConvertDebugDeclareToDebugValue ... Summary: Do not convert a DbgDeclare to DbgValue if the store instruction only refer to a fragment of the variable described by the DbgDeclare. Problem was seen when for example having an alloca for an array or struct, and there were stores to individual elements. In the past we inserted a DbgValue intrinsics for each store, just as if the store wrote the whole variable. When handling store instructions we insert a DbgValue that indicates that the variable is "undefined", as we do not know which part of the variable that is updated by the store. When ConvertDebugDeclareToDebugValue is used with a load/phi instruction we assert that the referenced value is large enough to cover the whole variable. Afaict this should be true for all scenarios where those methods are used on trunk. If the assert blows in the future I guess we could simply skip to insert a dbg.value instruction. In the future I think we should examine which part of the variable that is accessed, and add a DbgValue instrinsic with an appropriate DW_OP_LLVM_fragment expression. Reviewers: dblaikie, aprantl, rnk Reviewed By: aprantl Subscribers: JDevlieghere, llvm-commits Tags: #debug-info Differential Revision: https://reviews.llvm.org/D48024 llvm-svn: 334704		2018-06-14 11:23:42 +00:00
..
llvm	[DebugInfo] Check size of variable in ConvertDebugDeclareToDebugValue	2018-06-14 11:23:42 +00:00
llvm-c	[DebugInfo] Refactoring DIType::setFlags to DIType::cloneWithFlags, NFC	2018-06-01 23:15:09 +00:00