summaryrefslogtreecommitdiffstats
path: root/llvm/test/tools/llvm-cxxfilt/underscore.test
diff options
context:
space:
mode:
authorChandler Carruth <chandlerc@gmail.com>2017-01-22 10:34:01 +0000
committerChandler Carruth <chandlerc@gmail.com>2017-01-22 10:34:01 +0000
commitb698d5964d64d185f34db451ddbfb0a89100e7db (patch)
treec865b86fff9ef65eb681c2b632fdb93b6eeaa1df /llvm/test/tools/llvm-cxxfilt/underscore.test
parentd4be9f4b8d2ca9d0525960629172e8cc9a792500 (diff)
downloadbcm5719-llvm-b698d5964d64d185f34db451ddbfb0a89100e7db.tar.gz
bcm5719-llvm-b698d5964d64d185f34db451ddbfb0a89100e7db.zip
[PM] Fix a really nasty bug introduced when adding PGO support to the
new PM's inliner. The bug happens when we refine an SCC after having computed a proxy for the FunctionAnalysisManager, and then proceed to compute fresh analyses for functions in the *new* SCC using the manager provided by the old SCC's proxy. *And* when we manage to mutate a function in this new SCC in a way that invalidates those analyses. This can be... challenging to reproduce. I've managed to contrive a set of functions that trigger this and added a test case, but it is a bit brittle. I've directly checked that the passes run in the expected ways to help avoid the test just becoming silently irrelevant. This gets the new PM back to passing the LLVM test suite after the PGO improvements landed. llvm-svn: 292757
Diffstat (limited to 'llvm/test/tools/llvm-cxxfilt/underscore.test')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud