summaryrefslogtreecommitdiffstats
path: root/llvm/lib/DebugInfo/CodeView/DebugStringTableSubsection.cpp
diff options
context:
space:
mode:
authorJordan Rose <jordan_rose@apple.com>2018-03-23 18:05:19 +0000
committerJordan Rose <jordan_rose@apple.com>2018-03-23 18:05:19 +0000
commitdc86de6b6e3f34c669296f4b4fbc87075c41cc8e (patch)
treecd4df1914575f98962ab28dc00b6df6af0da0600 /llvm/lib/DebugInfo/CodeView/DebugStringTableSubsection.cpp
parent80f10e4fe5987cda01724ba9663b6d96754e3169 (diff)
downloadbcm5719-llvm-dc86de6b6e3f34c669296f4b4fbc87075c41cc8e.tar.gz
bcm5719-llvm-dc86de6b6e3f34c669296f4b4fbc87075c41cc8e.zip
Delete the copy constructor for llvm::yaml::Node
The nodes keep a reference back to the original document, but the document is streamed, not read all into memory at once, and the position is part of the state. If nodes are ever copied, the document position can end up being advanced more than once. This did not reveal any problems in LLVM or Clang but caught a handful over in Swift! llvm-svn: 328345
Diffstat (limited to 'llvm/lib/DebugInfo/CodeView/DebugStringTableSubsection.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud