diff options
author | Michael Spencer <michael_spencer@apple.com> | 2019-10-28 14:26:45 -0700 |
---|---|---|
committer | Michael Spencer <bigcheesegs@gmail.com> | 2020-01-23 16:58:50 -0800 |
commit | 356a4b433bf7224666fd7152a8ad2560fb286ef4 (patch) | |
tree | 42d1f687bcdeb5fb243e506b75ac7ca57246e006 /lldb/unittests/ScriptInterpreter/Python | |
parent | 2531535984ad989ce88aeee23cb92a827da6686e (diff) | |
download | llvm-356a4b433bf7224666fd7152a8ad2560fb286ef4.zip llvm-356a4b433bf7224666fd7152a8ad2560fb286ef4.tar.gz llvm-356a4b433bf7224666fd7152a8ad2560fb286ef4.tar.bz2 |
[clang][clang-scan-deps] Aggregate the full dependency information.
Differential Revision: https://reviews.llvm.org/D70268
This is a recommit of f978ea498309 with a fix for the PowerPC failure.
The issue was that:
* `CompilerInstance::ExecuteAction` calls
`getTarget().adjust(getLangOpts());`.
* `PPCTargetInfo::adjust` changes `LangOptions::HasAltivec`.
* This happens after the first few calls to `getModuleHash`.
There’s even a FIXME saying:
```
// FIXME: We shouldn't need to do this, the target should be immutable once
// created. This complexity should be lifted elsewhere.
```
This only showed up on PowerPC because it's one of the few targets that
almost always changes a hashed langopt.
I looked into addressing the fixme, but that would be a much larger
change, and it's not the only thing that happens in `ExecuteAction` that
can change the module context hash. Instead I changed the code to not
call `getModuleHash` until after it has been modified in `ExecuteAction`.
Diffstat (limited to 'lldb/unittests/ScriptInterpreter/Python')
0 files changed, 0 insertions, 0 deletions