summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/lang/cpp
diff options
context:
space:
mode:
authorBenjamin Kramer <benny.kra@googlemail.com>2017-07-24 16:18:09 +0000
committerBenjamin Kramer <benny.kra@googlemail.com>2017-07-24 16:18:09 +0000
commitfc638c11bbb6e1202bfd7862413f6b8d2067100e (patch)
tree97e4fcc2e6b04825223377e2fddb714be4c0cbb8 /lldb/packages/Python/lldbsuite/test/lang/cpp
parent898ddf61c054ec67c4966d8471dc4751d1a361c9 (diff)
downloadbcm5719-llvm-fc638c11bbb6e1202bfd7862413f6b8d2067100e.tar.gz
bcm5719-llvm-fc638c11bbb6e1202bfd7862413f6b8d2067100e.zip
[CodeGenPrepare] Cut off FindAllMemoryUses if there are too many uses.
This avoids excessive compile time. The case I'm looking at is Function.cpp from an old version of LLVM that still had the giant memcmp string matcher in it. Before r308322 this compiled in about 2 minutes, after it, clang takes infinite* time to compile it. With this patch we're at 5 min, which is still bad but this is a pathological case. The cut off at 20 uses was chosen by looking at other cut-offs in LLVM for user scanning. It's probably too high, but does the job and is very unlikely to regress anything. Fixes PR33900. * I'm impatient and aborted after 15 minutes, on the bug report it was killed after 2h. llvm-svn: 308891
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/lang/cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud