summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/expression_command/call-function/main.cpp
diff options
context:
space:
mode:
authorSergei Larin <slarin@codeaurora.org>2016-01-22 21:18:20 +0000
committerSergei Larin <slarin@codeaurora.org>2016-01-22 21:18:20 +0000
commit94be2dee7ec126ed833599c7c7b88f045b02dcd1 (patch)
tree1ce11622610fcb978c5d41b6f7fe63f1cb6e51a3 /lldb/packages/Python/lldbsuite/test/expression_command/call-function/main.cpp
parentaa5d08d04bcb05a6fb34e22aa47d73d0f2641b8f (diff)
downloadbcm5719-llvm-94be2dee7ec126ed833599c7c7b88f045b02dcd1.tar.gz
bcm5719-llvm-94be2dee7ec126ed833599c7c7b88f045b02dcd1.zip
Make sure that any new and optimized objects created during GlobalOPT copy all the attributes from the base object.
Summary: Make sure that any new and optimized objects created during GlobalOPT copy all the attributes from the base object. A good example of improper behavior in the current implementation is section information associated with the GlobalObject. If a section was set for it, and GlobalOpt is creating/modifying a new object based on this one (often copying the original name), without this change new object will be placed in a default section, resulting in inappropriate properties of the new variable. The argument here is that if customer specified a section for a variable, any changes to it that compiler does should not cause it to change that section allocation. Moreover, any other properties worth representation in copyAttributesFrom() should also be propagated. Reviewers: jmolloy, joker-eph, joker.eph Subscribers: slarin, joker.eph, rafael, tobiasvk, llvm-commits Differential Revision: http://reviews.llvm.org/D16074 llvm-svn: 258556
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/expression_command/call-function/main.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud