RISC-V uses a post-select peephole pass to optimise
(load/store (ADDI $reg, %lo(addr)), 0) into (load/store $reg, %lo(addr)).
This peephole wasn't firing for accesses to constant pools, which is how we
materialise most floating point constants.
This adds support for the constantpool case, which improves code generation for
lots of small FP loading examples. I have not added any tests because this
structure is well-covered by the fp-imm.ll testcases, as well as almost
all other uses of floating point constants in the RISC-V backend tests.