summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/symbol-context/TestSymbolContext.py
diff options
context:
space:
mode:
authorSimon Tatham <simon.tatham@arm.com>2019-11-04 12:40:25 +0000
committerSimon Tatham <simon.tatham@arm.com>2019-11-06 09:01:42 +0000
commitf0c6890f32c0d5ee7f3973181eb83fcb0a50dc1a (patch)
tree811343cf6055c265db6eeaa220a9819848405c53 /lldb/packages/Python/lldbsuite/test/python_api/symbol-context/TestSymbolContext.py
parent26bc7cb05edd6bea4b9a1593baf0fbe9e45f54e4 (diff)
downloadbcm5719-llvm-f0c6890f32c0d5ee7f3973181eb83fcb0a50dc1a.tar.gz
bcm5719-llvm-f0c6890f32c0d5ee7f3973181eb83fcb0a50dc1a.zip
[ARM,MVE] Integer-type nitpicks in MVE intrinsics.
A few integer types in the ACLE definitions of MVE intrinsics are given as 'int' or 'unsigned' instead of <stdint.h> fixed-size types like uint32_t. Usually these are the ones where the size isn't that important, such as immediate offsets in loads (which have a range limited by the instruction encoding) or the carry flag in vadcq which can only be 0 or 1 anyway. With this change, <arm_mve.h> follows that exact type naming, so that the function prototypes look identical to the ones in ACLE, instead of replacing int and unsigned with int32_t and uint32_t. Reviewers: dmgreen Subscribers: kristof.beyls, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D69790
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/symbol-context/TestSymbolContext.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud