summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/commands/command/script/main.cpp
diff options
context:
space:
mode:
authorVedant Kumar <vsk@apple.com>2019-10-18 23:33:40 +0000
committerVedant Kumar <vsk@apple.com>2019-10-18 23:33:40 +0000
commit937241b0d9e8f896d4387292f01abf18ba9f9fcb (patch)
treef73007ceb14c1d809a7ce716ad9c5006f8eb193d /lldb/packages/Python/lldbsuite/test/commands/command/script/main.cpp
parentd4274f0174ff152490195fa2a65e4087deae3dd4 (diff)
downloadbcm5719-llvm-937241b0d9e8f896d4387292f01abf18ba9f9fcb.tar.gz
bcm5719-llvm-937241b0d9e8f896d4387292f01abf18ba9f9fcb.zip
[profile] Do not cache __llvm_profile_get_filename result
When the %m filename pattern is used, the filename is unique to each image, so the cached value is wrong. It struck me that the full filename isn't something that's recomputed often, so perhaps it doesn't need to be cached at all. David Li pointed out we can go further and just hide lprofCurFilename. This may regress workflows that depend on using the set-filename API to change filenames across all loaded DSOs, but this is expected to be very rare. rdar://55137071 Differential Revision: https://reviews.llvm.org/D69137 llvm-svn: 375301
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/commands/command/script/main.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud