diff options
author | Simon Tatham <simon.tatham@arm.com> | 2020-01-06 16:33:05 +0000 |
---|---|---|
committer | Simon Tatham <simon.tatham@arm.com> | 2020-01-06 16:33:07 +0000 |
commit | 4978296cd8e4d10724cfa41f0308d256c0fd490c (patch) | |
tree | 1f5177a9a931de2d0b087c84e8ac4854c6543798 /lldb/packages/Python/lldbsuite/test/python_api/signals/main.cpp | |
parent | b99ef32d041c992d0cb192bdee3e16b9a56de3a9 (diff) | |
download | bcm5719-llvm-4978296cd8e4d10724cfa41f0308d256c0fd490c.tar.gz bcm5719-llvm-4978296cd8e4d10724cfa41f0308d256c0fd490c.zip |
[ARM,MVE] Support -ve offsets in gather-load intrinsics.
Summary:
The ACLE intrinsics with `gather_base` or `scatter_base` in the name
are wrappers on the MVE load/store instructions that take a vector of
base addresses and an immediate offset. The immediate offset can be up
to 127 times the alignment unit, and it can be positive or negative.
At the MC layer, we got that right. But in the Sema error checking for
the wrapping intrinsics, the offset was erroneously constrained to be
positive.
To fix this I've adjusted the `imm_mem7bit` class in the Tablegen that
defines the intrinsics. But that causes integer literals like
`0xfffffffffffffe04` to appear in the autogenerated calls to
`SemaBuiltinConstantArgRange`, which provokes a compiler warning
because that's out of the non-overflowing range of an `int64_t`. So
I've also tweaked `MveEmitter` to emit that as `-0x1fc` instead.
Updated the tests of the Sema checks themselves, and also adjusted a
random sample of the CodeGen tests to actually use negative offsets
and prove they get all the way through code generation without causing
a crash.
Reviewers: dmgreen, miyuki, MarkMurrayARM
Reviewed By: dmgreen
Subscribers: kristof.beyls, cfe-commits, llvm-commits
Tags: #clang, #llvm
Differential Revision: https://reviews.llvm.org/D72268
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/signals/main.cpp')
0 files changed, 0 insertions, 0 deletions