summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/lang/cpp/breakpoint-commands/nested.cpp
diff options
context:
space:
mode:
authorFedor Sergeev <fedor.sergeev@azul.com>2018-12-21 11:49:05 +0000
committerFedor Sergeev <fedor.sergeev@azul.com>2018-12-21 11:49:05 +0000
commit2d94c2265ebd3ed4cd964a3a2f21486b1b6463f8 (patch)
tree8d38acb35dc14e14d81825f549864d9d8a741caf /lldb/packages/Python/lldbsuite/test/lang/cpp/breakpoint-commands/nested.cpp
parent41a9e53500c4317da7fa0d0b52322ea5df78a796 (diff)
downloadbcm5719-llvm-2d94c2265ebd3ed4cd964a3a2f21486b1b6463f8.tar.gz
bcm5719-llvm-2d94c2265ebd3ed4cd964a3a2f21486b1b6463f8.zip
[NewPM] -print-module-scope -print-after now prints module even after invalidated Loop/SCC
-print-after IR printing generally can not print the IR unit (Loop or SCC) which has just been invalidated by the pass. However, when working in -print-module-scope mode even if Loop was invalidated there is still a valid module that we can print. Since we can not access invalidated IR unit from AfterPassInvalidated instrumentation point we can remember the module to be printed *before* pass. This change introduces BeforePass instrumentation that stores all the information required for module printing into the stack and then after pass (in AfterPassInvalidated) just print whatever has been placed on stack. Reviewed By: philip.pfaffe Differential Revision: https://reviews.llvm.org/D55278 llvm-svn: 349896
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/lang/cpp/breakpoint-commands/nested.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud