summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/signals/TestSignalsAPI.py
diff options
context:
space:
mode:
authorSam Elliott <selliott@lowrisc.org>2019-08-01 12:42:31 +0000
committerSam Elliott <selliott@lowrisc.org>2019-08-01 12:42:31 +0000
commitf596f45070a0db27c431b0585248f61a40acbb1c (patch)
treecd28e6655fd3d1b7d3a8817209372bfddbcc64e3 /lldb/packages/Python/lldbsuite/test/python_api/signals/TestSignalsAPI.py
parent208ebc9e8b661d11ac6790184f17d5a1b5c368e5 (diff)
downloadbcm5719-llvm-f596f45070a0db27c431b0585248f61a40acbb1c.tar.gz
bcm5719-llvm-f596f45070a0db27c431b0585248f61a40acbb1c.zip
[RISCV] Add Custom Parser for Atomic Memory Operands
Summary: GCC Accepts both (reg) and 0(reg) for atomic instruction memory operands. These instructions do not allow for an offset in their encoding, so in the latter case, the 0 is silently dropped. Due to how we have structured the RISCVAsmParser, the easiest way to add support for parsing this offset is to add a custom AsmOperand and parser. This parser drops all the parens, and just keeps the register. This commit also adds a custom printer for these operands, which matches the GCC canonical printer, printing both `(a0)` and `0(a0)` as `(a0)`. Reviewers: asb, lewis-revill Reviewed By: asb Subscribers: s.egerton, hiraditya, rbar, johnrusso, simoncook, apazos, sabuasal, niosHD, kito-cheng, shiva0217, jrtc27, MaskRay, zzheng, edward-jones, rogfer01, MartinMosbeck, brucehoult, the_o, rkruppe, jfb, PkmX, jocewei, psnobl, benna, Jim, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D65205 llvm-svn: 367553
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/signals/TestSignalsAPI.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud