https://github.com/maksfb commented:
I expect that eventually we will get RISC-V support for jump tables. In this context, I would prefer to keep the format of the jump table itself separate from the underlying architecture. I.e. we can use JTs with an absolute 64-bit addressing on any platform with a proper compiler support. Having one type, e.g. `JTT_ABS64`, sounds more convenient. And we can always lookup the target architecture if needed, but again it should be orthogonal to the format itself. What could be different is endianness, but we can handle it during serialization. Also, in most places we use the number of bits for naming "things". Let's stick to this scheme. https://github.com/llvm/llvm-project/pull/132109 _______________________________________________ llvm-branch-commits mailing list llvm-branch-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
