[llvm] [feature][riscv] handle target address calculation in llvm-objdump disassembly for riscv (PR #144620)

Arjun Patel via llvm-commits llvm-commits at lists.llvm.org
Sun Aug 24 23:49:00 PDT 2025


================
@@ -0,0 +1,110 @@
+# RUN: llvm-mc -riscv-add-build-attributes -triple=riscv64 -filetype=obj -mattr=+d,+c,+zcb %s -o %t
----------------
arjunUpatel wrote:

I'm failing to see how different endianness will lead to different results here. The implementation keeps track of the value written to registers by saving the immediate values passed to instructions. Shouldn't the burden of correctness fall on the disassmbler to report the correct immediate value in the populated `MCInst`?

Am I overlooking something very obvious or just comically wrong?

https://github.com/llvm/llvm-project/pull/144620


More information about the llvm-commits mailing list