diff options
| author | Wei Mi <wmi@google.com> | 2018-10-23 23:29:45 +0000 |
|---|---|---|
| committer | Wei Mi <wmi@google.com> | 2018-10-23 23:29:45 +0000 |
| commit | 80a0c97e07bd2057e163ec3e53702e458803a03b (patch) | |
| tree | 299ee87691d2a246e474d8574fac6210f2917ad7 /lldb/packages/Python/lldbsuite/support/optional_with.py | |
| parent | 4f82406c460d7b302fed395464d6649dc6aea05e (diff) | |
| download | bcm5719-llvm-80a0c97e07bd2057e163ec3e53702e458803a03b.tar.gz bcm5719-llvm-80a0c97e07bd2057e163ec3e53702e458803a03b.zip | |
[PM] keeping history when original SCC split and then merge into itself
in the same round of SCC update.
In https://reviews.llvm.org/rL309784, inline history is added to prevent
infinite inlining across multiple run of inliner and SCC update, but the
history will only be kept when new SCC is actually generated during SCC update.
We found a case that SCC can be split and then merge into itself in the same
round of SCC update, so the same SCC will be pop out from UR.CWorklist and
then added back immediately, without any new SCC generated, that is why the
existing patch cannot catch the infinite inline case.
What the patch does is even if no new SCC is generated, if only the current
SCC appears in UR.CWorklist again, then keep the inline history.
Differential Revision: https://reviews.llvm.org/D52915
llvm-svn: 345103
Diffstat (limited to 'lldb/packages/Python/lldbsuite/support/optional_with.py')
0 files changed, 0 insertions, 0 deletions
