[llvm] [RISCV] Pick correct lround libcall for fp128 (PR #213220)

[Kane Wang via llvm-commits]

================
@@ -0,0 +1,133 @@
+; NOTE: Assertions have been autogenerated by utils/update_llc_test_checks.py
----------------
ReVe1uv wrote:

> Can we put this in fp128.ll?
I'd like to fold this into fp128.ll, but it currently only has an RV32I RUN line, and the bug only triggers on rv64 (the i32-result custom path). Under RV32I the result is legal and takes the generic path, which was already correct, so it wouldn't actually exercise the buggy path. Should I add an RV64 RUN line to fp128.ll, or keep rv64 coverage in a separate file?


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