diff options
| author | Alex Bradbury <asb@igalia.com> | 2025-03-28 19:23:56 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-03-28 19:23:56 +0000 |
| commit | 4e4cb4359ae915b5a14c94914e39a8cc94e98963 (patch) | |
| tree | d4ab1963735000d803e7cb8b5698ff0b16fc1319 /llvm/lib/Target/RISCV/Disassembler/RISCVDisassembler.cpp | |
| parent | da84a7d4038177152082265c0d425866a4f71659 (diff) | |
| download | llvm-4e4cb4359ae915b5a14c94914e39a8cc94e98963.zip llvm-4e4cb4359ae915b5a14c94914e39a8cc94e98963.tar.gz llvm-4e4cb4359ae915b5a14c94914e39a8cc94e98963.tar.bz2 | |
[RISCV][MC] Enable printing of zext.b alias (#133502)
The comment shows that at the time we were worried about producing the
alias in assembly that might be ingested by a binutils version that
doesn't yet support it. binutils gained support over 4 years ago
<https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=c2137f55ad04e451d834048d4bfec1de2daea20e>.
With all the changes in areas such as ELF attributes, if you tried to
use LLVM's RISC-V assembler output with a binutils that old then zext.b
would be the least of your worries.
Diffstat (limited to 'llvm/lib/Target/RISCV/Disassembler/RISCVDisassembler.cpp')
0 files changed, 0 insertions, 0 deletions