diff options
| author | Chandler Carruth <chandlerc@gmail.com> | 2016-03-10 11:24:11 +0000 |
|---|---|---|
| committer | Chandler Carruth <chandlerc@gmail.com> | 2016-03-10 11:24:11 +0000 |
| commit | 4c660f70870023d62e5fd353c7038359fd23391e (patch) | |
| tree | 544bae0a5bdc791c067b8446191caf77350bffc5 /lldb/packages/Python/lldbsuite/test/lock.py | |
| parent | b95def749141e0d5c5985be74c3fb2a4ae308fb0 (diff) | |
| download | llvm-4c660f70870023d62e5fd353c7038359fd23391e.zip llvm-4c660f70870023d62e5fd353c7038359fd23391e.tar.gz llvm-4c660f70870023d62e5fd353c7038359fd23391e.tar.bz2 | |
[CG] Add a new pass manager printer pass for the old call graph and
actually finish wiring up the old call graph.
There were bugs in the old call graph that hadn't been caught because it
wasn't being tested. It wasn't being tested because it wasn't in the
pipeline system and we didn't have a printing pass to run in tests. This
fixes all of that.
As for why I'm still keeping the old call graph alive its so that I can
port GlobalsAA to the new pass manager with out forking it to work with
the lazy call graph. That's clearly the right eventual design, but it
seems pragmatic to defer that until its necessary. The old call graph
works just fine for GlobalsAA.
llvm-svn: 263104
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/lock.py')
0 files changed, 0 insertions, 0 deletions