diff options
| author | Pavel Labath <pavel@labath.sk> | 2020-07-06 16:44:37 +0200 |
|---|---|---|
| committer | Pavel Labath <pavel@labath.sk> | 2020-07-23 14:17:57 +0200 |
| commit | 9cdd68e7c1331efd3c0aec84ef925a1679a73771 (patch) | |
| tree | 468085f6b4edc9c30e74fed366f24b24e761ddbb /llvm/lib/CodeGen/TargetLoweringObjectFileImpl.cpp | |
| parent | 697c6d8907e781534eeff062fbe90806ece4b25c (diff) | |
| download | llvm-9cdd68e7c1331efd3c0aec84ef925a1679a73771.zip llvm-9cdd68e7c1331efd3c0aec84ef925a1679a73771.tar.gz llvm-9cdd68e7c1331efd3c0aec84ef925a1679a73771.tar.bz2 | |
Recommit "[lldb/API] Overwrite variables with SBLaunchInfo::SetEnvironment(append=true)"
The patch was reverted 27d52cd86a2c because of failures in
TestWeakSymbols.py. These have now been addressed in D83552.
The original commit message was:
This function was documented to overwrite entries with D76111, which was
adding a couple of similar functions. However, this function (unlike the
functions added in that patch) was/is not actually overwriting variables
-- any pre-existing variables would get ignored.
This behavior does not seem to be intentional. In fact, before the refactor in
D41359, this function could introduce duplicate entries, which could
have very surprising effects both inside lldb and on other applications
(some applications would take the first value, some the second one; in
lldb, attempting to unset a variable could make the second variable
become active, etc.).
Overwriting seems to be the most reasonable behavior here, so change the
code to match documentation.
Differential Revision: https://reviews.llvm.org/D83306
Diffstat (limited to 'llvm/lib/CodeGen/TargetLoweringObjectFileImpl.cpp')
0 files changed, 0 insertions, 0 deletions