summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/expression_command/rdar44436068/Test128BitsInteger.py
diff options
context:
space:
mode:
authorArtem Dergachev <artem.dergachev@gmail.com>2018-10-15 17:53:18 +0000
committerArtem Dergachev <artem.dergachev@gmail.com>2018-10-15 17:53:18 +0000
commitfcf107d411d7e79ebafc3f9ad1289ed481358f44 (patch)
treeeda6535331290980f373ec77283e1bde89373664 /lldb/packages/Python/lldbsuite/test/expression_command/rdar44436068/Test128BitsInteger.py
parent65b4d7ddd9bc04c239ed344c0a3bbb7a46e81887 (diff)
downloadbcm5719-llvm-fcf107d411d7e79ebafc3f9ad1289ed481358f44.tar.gz
bcm5719-llvm-fcf107d411d7e79ebafc3f9ad1289ed481358f44.zip
[analyzer] Teach CallEvent about C++17 aligned operator new().
In C++17, when class C has large alignment value, a special case of overload resolution rule kicks in for expression new C that causes the aligned version of operator new() to be called. The aligned new has two arguments: size and alignment. However, the new-expression has only one "argument": the construct-expression for C(). This causes a false positive in core.CallAndMessage's check for matching number of arguments and number of parameters. Update CXXAllocatorCall, which is a CallEvent sub-class for operator new calls within new-expressions, so that the number of arguments always matched the number of parameters. rdar://problem/44738501 Differential Revision: https://reviews.llvm.org/D52957 llvm-svn: 344539
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/expression_command/rdar44436068/Test128BitsInteger.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud