summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/expression_command/call-function
diff options
context:
space:
mode:
authorDavid Blaikie <dblaikie@gmail.com>2016-05-25 23:37:06 +0000
committerDavid Blaikie <dblaikie@gmail.com>2016-05-25 23:37:06 +0000
commit1fc3e6bda225f4dfcf7423564008efaa4350de8c (patch)
treee82fd967b172d3088432498ea37be51e8eaa1b89 /lldb/packages/Python/lldbsuite/test/expression_command/call-function
parent9d4ea6df8bccf76fbc62db504bb43c3fb8eec9b0 (diff)
downloadbcm5719-llvm-1fc3e6bda225f4dfcf7423564008efaa4350de8c.tar.gz
bcm5719-llvm-1fc3e6bda225f4dfcf7423564008efaa4350de8c.zip
llvm-dwp: Ensure uncompressed sections are not relocated during processing of later inputs
Richard Smith identified this in post commit review of r270466. The string sections in particular (in the future, possibly all sections - so I'm not going to bother pulling out just the string sections for the extra lifetime handling right now) need to remain valid during processing of all inputs so that elements of the DWPStringPool can be looked up repeatedly without having to make in-memory copies of string contents in the noncompressed case (more common in dwp+dwp merge steps where the memory is a bigger problem because the files are larger). Using the SmallVector (or any vector) a reallocation on push_back could cause any of the nested SmallStrings in small mode to move in memory and invalid pointers to their contents. Using a deque the SmallStrings will never move around since no elements are removed from the container. llvm-svn: 270797
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/expression_command/call-function')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud