diff options
| author | Ulrich Weigand <ulrich.weigand@de.ibm.com> | 2020-03-31 19:41:04 +0200 |
|---|---|---|
| committer | Ulrich Weigand <ulrich.weigand@de.ibm.com> | 2020-03-31 19:48:50 +0200 |
| commit | c726c920e04046da29e403d55aa9c0e466b13959 (patch) | |
| tree | e258376079271cc40e9d58b1e486363e512640fd /lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp | |
| parent | dc817b2dea9f28e22470d1d74956f404fcec4e01 (diff) | |
| download | llvm-c726c920e04046da29e403d55aa9c0e466b13959.zip llvm-c726c920e04046da29e403d55aa9c0e466b13959.tar.gz llvm-c726c920e04046da29e403d55aa9c0e466b13959.tar.bz2 | |
[SystemZ] Allow %r0 in address context for AsmParser
Registers used in any address (as well as in a few other contexts)
have special semantics when a "zero" register is used, which is
why the back-end defines extra register classes ADDR32, ADDR64 etc
to be used to prevent the register allocator from using %r0 there.
However, when writing assembler code "by hand", you sometimes need
to trigger that special semantics. However, currently the AsmParser
will reject %r0 in those places. In some cases it may be possible
to write that instruction differently - but in others it is currently
not possible at all.
This check in AsmParser simply seems overly strict, so this patch
just removes the check completely. This brings the behaviour of
AsmParser in line with the GNU assembler as well.
Bugzilla: https://bugs.llvm.org/show_bug.cgi?id=45092
Diffstat (limited to 'lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp')
0 files changed, 0 insertions, 0 deletions