summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/value/TestValueAPI.py
diff options
context:
space:
mode:
authorVedant Kumar <vsk@apple.com>2017-02-25 06:35:45 +0000
committerVedant Kumar <vsk@apple.com>2017-02-25 06:35:45 +0000
commit502bbfafcaca191f13576ce8eb767c96c7b510a5 (patch)
tree5213cb9b998c7dc51240222d5f0c0cd0d6a95ba7 /lldb/packages/Python/lldbsuite/test/python_api/value/TestValueAPI.py
parent4284ce1348e075ddf5be18a3e94946a9a425afa6 (diff)
downloadbcm5719-llvm-502bbfafcaca191f13576ce8eb767c96c7b510a5.tar.gz
bcm5719-llvm-502bbfafcaca191f13576ce8eb767c96c7b510a5.zip
Retry: [profiling] Fix profile counter increment when emitting selects (PR32019)
2nd attempt: the first was in r296231, but it had a use after lifetime bug. Clang has logic to lower certain conditional expressions directly into llvm select instructions. However, it does not emit the correct profile counter increment as it does this: it emits an unconditional increment of the counter for the 'then branch', even if the value selected is from the 'else branch' (this is PR32019). That means, given the following snippet, we would report that "0" is selected twice, and that "1" is never selected: int f1(int x) { return x ? 0 : 1; ^2 ^0 } f1(0); f1(1); Fix the problem by using the instrprof_increment_step intrinsic to do the proper increment. llvm-svn: 296245
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/value/TestValueAPI.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud