summaryrefslogtreecommitdiff
path: root/clang/test/CodeGen/Inputs/thinlto_expect1.proftext
AgeCommit message (Collapse)Author
2020-07-30[PGO] Include the mem ops into the function hash.Hiroshi Yamauchi
To avoid hash collisions when the only difference is in mem ops.
2020-07-29Revert "[PGO] Include the mem ops into the function hash."Hiroshi Yamauchi
This reverts commit 120e66b3418b37b95fc1dbbb23e296a602a24fa8. Due to a buildbot failure.
2020-07-29[PGO] Include the mem ops into the function hash.Hiroshi Yamauchi
To avoid hash collisions when the only difference is in mem ops. Differential Revision: https://reviews.llvm.org/D84782
2020-01-14[remark][diagnostics] Using clang diagnostic handler for IR input filesRong Xu
For IR input files, we currently use LLVM diagnostic handler even the compilation is from clang. As a result, we are not able to use -Rpass to get the transformation reports. Some warnings are not handled properly either: We found many mysterious warnings in our ThinLTO backend compilations in SamplePGO and CSPGO. An example of the warning: "warning: net/proto2/public/metadata_lite.h:51:21: 0.02% (1 / 4999)" This turns out to be a warning by Wmisexpect, which is supposed to be filtered out by default. But since the filter is in clang's diagnostic hander, we emit these incomplete warnings from LLVM's diagnostic handler. This patch uses clang diagnostic handler for IR input files. We create a fake backendconsumer just to install the diagnostic handler. With this change, we will have proper handling of all the warnings and we can use -Rpass* options in IR input files compilation. Also note that with is patch, LLVM's diagnostic options, like "-mllvm -pass-remarks=*", are no longer be able to get optimization remarks. Differential Revision: https://reviews.llvm.org/D72523