forked from OSchip/llvm-project
[GlobalsAA] Fix a pretty terrible bug that has been in GlobalsAA for
a long time. The key thing is that we need to create value handles for every function that we create a `FunctionInfo` object around. Without this, when that function is deleted we can end up creating a new function that collides with its address and look up a stale AA result. With that AA result we can in turn miscompile code in ways that break. This is seriously one of the most absurd miscompiles I've seen. It only reproduced for us recently and only when building a very large server with both ThinLTO and PGO. A *HUGE* shout out to Wei Mi who tracked all of this down and came up with this patch. I'm just landing it because I happened to still by at a computer. He or I can work on crafting a test case to hit this (now that we know what to target) but it'll take a while, and we've been chasing this for a long time and need it fix Right Now. llvm-svn: 327761
This commit is contained in:
parent
b3e7dc9144
commit
196a9fab82
|
@ -502,6 +502,8 @@ void GlobalsAAResult::AnalyzeCallGraph(CallGraph &CG, Module &M) {
|
|||
}
|
||||
|
||||
FunctionInfo &FI = FunctionInfos[F];
|
||||
Handles.emplace_front(*this, F);
|
||||
Handles.front().I = Handles.begin();
|
||||
bool KnowNothing = false;
|
||||
|
||||
// Collect the mod/ref properties due to called functions. We only compute
|
||||
|
|
Loading…
Reference in New Issue