diff options
| author | Duncan P. N. Exon Smith <dexonsmith@apple.com> | 2016-04-17 19:40:20 +0000 |
|---|---|---|
| committer | Duncan P. N. Exon Smith <dexonsmith@apple.com> | 2016-04-17 19:40:20 +0000 |
| commit | 0fdaf8c9c263857a775f58aa3aac7a94d70f8b5f (patch) | |
| tree | a1413225a4b97dd486cda5cc84f438b87911aec0 /lldb/packages/Python/lldbsuite/test/expression_command/call-function/TestCallStdStringFunction.py | |
| parent | caa11696535d1e03ce6be057c514f672498157e8 (diff) | |
| download | bcm5719-llvm-0fdaf8c9c263857a775f58aa3aac7a94d70f8b5f.tar.gz bcm5719-llvm-0fdaf8c9c263857a775f58aa3aac7a94d70f8b5f.zip | |
Linker: Don't double-schedule appending variables
Add an assertion to ValueMapper that prevents double-scheduling of
GlobalValues to remap, and fix the one place it happened. There are
tons of tests that fail with this assertion in place and without the
code change, so I'm not adding another.
Although it looks related, r266563 was, indeed, removing dead code.
AFAICT, this cross-file double-scheduling started in r266510 when the
cross-file recursion was removed.
llvm-svn: 266569
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/expression_command/call-function/TestCallStdStringFunction.py')
0 files changed, 0 insertions, 0 deletions
