summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/sbstructureddata/TestStructuredDataAPI.py
diff options
context:
space:
mode:
authorZi Xuan Wu <wuzish@cn.ibm.com>2018-11-16 03:00:00 +0000
committerZi Xuan Wu <wuzish@cn.ibm.com>2018-11-16 03:00:00 +0000
commit64d85a29edd8db3d9fa5421b8c7edb1ed12c0c76 (patch)
tree2b882b4d55f1df91aec0e970884057c4902ca145 /lldb/packages/Python/lldbsuite/test/python_api/sbstructureddata/TestStructuredDataAPI.py
parent6284aee9f811d596b941e44b30dee5befbc22f20 (diff)
downloadbcm5719-llvm-64d85a29edd8db3d9fa5421b8c7edb1ed12c0c76.tar.gz
bcm5719-llvm-64d85a29edd8db3d9fa5421b8c7edb1ed12c0c76.zip
[Clang][Sema]Choose a better candidate in overload function call if there is a compatible vector conversion instead of ambiguous call error
There are 2 function variations with vector type parameter. When we call them with argument of different vector type we would prefer to choose the variation with implicit argument conversion of compatible vector type instead of incompatible vector type. For example, typedef float __v4sf __attribute__((__vector_size__(16))); void f(vector float); void f(vector signed int); int main { __v4sf a; f(a); } Here, we'd like to choose f(vector float) but not report an ambiguous call error. Differential revision: https://reviews.llvm.org/D53417 llvm-svn: 347019
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/sbstructureddata/TestStructuredDataAPI.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud