Follow up to fix in r311023, which fixed the case where the combined
index is written to disk. The same samplePGO logic exists for the
in-memory index when computing imports, so we need to filter out
GlobalVariable summaries there too.
Details
Diff Detail
- Build Status
Buildable 9437 Build 9437: arc lint + arc unit
Event Timeline
test/Transforms/FunctionImport/Inputs/funcimport_var2.ll | ||
---|---|---|
3 | Yes, this is required when going through llvm-lto2. | |
test/Transforms/FunctionImport/funcimport_var.ll | ||
8 | A lot of llvm-lto2 test lines are structured this way so that it is easier to see the symbol resolutions. | |
10 | llvm-lto uses the legacy LTO interface, which is still used by ld64 and some other custom linkers. llvm-lto2 tests the new linker resolution based LTO interface, which is used by gold and lld. Therefore it is required that resolutions for each symbol are provided. In general I think it is good to test with llvm-lto2 as well. Note that the version of the bug I am fixing can also be tested via llvm-lto via the "run" action which passes the index in-memory, so I have added that as well. Additionally, I am piping an output ELF for each through llvm-nm with a simple CHECK, since someone once told me this was good form to make sure that the expected output was created. |
Are these necessary?