mirror of
https://github.com/RPCS3/llvm.git
synced 2025-01-25 12:04:36 +00:00
[ThinLTO] Fix bot failures by avoiding threaded map modifications
Ensure multiple threads won't have to modify map, probable cause of bot failures from r270584 such as: http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-fast/builds/13095 git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@270595 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
parent
d7b9b912dd
commit
82332cd02e
@ -937,10 +937,12 @@ void ThinLTOCodeGenerator::run() {
|
||||
// Changes are made in the index, consumed in the ThinLTO backends.
|
||||
thinLTOInternalizeAndPromoteInIndex(*Index, isExported);
|
||||
|
||||
// Make sure that every module has an entry in the ExportLists to enable
|
||||
// threaded access to this map below
|
||||
for (auto &DefinedGVSummaries : ModuleToDefinedGVSummaries)
|
||||
// Make sure that every module has an entry in the ExportLists and
|
||||
// ResolvedODR maps to enable threaded access to these maps below.
|
||||
for (auto &DefinedGVSummaries : ModuleToDefinedGVSummaries) {
|
||||
ExportLists[DefinedGVSummaries.first()];
|
||||
ResolvedODR[DefinedGVSummaries.first()];
|
||||
}
|
||||
|
||||
// Compute the ordering we will process the inputs: the rough heuristic here
|
||||
// is to sort them per size so that the largest module get schedule as soon as
|
||||
|
Loading…
x
Reference in New Issue
Block a user