Re: [PATCH] RISC-V: Fix riscv_modes_tieable_p

2025-01-10 Thread Jeff Law
On 1/10/25 4:59 PM, Palmer Dabbelt wrote: On Fri, 10 Jan 2025 12:21:15 PST (-0800), jeffreya...@gmail.com wrote: On 1/10/25 12:11 PM, Robin Dapp wrote: Integer values and floating-point values need to be converted by fmv series instructions. So if mode1 is MODE_INT and mode2 is MODE_FLOAT,

Re: [PATCH] RISC-V: Fix riscv_modes_tieable_p

2025-01-10 Thread Palmer Dabbelt
On Fri, 10 Jan 2025 12:21:15 PST (-0800), jeffreya...@gmail.com wrote: On 1/10/25 12:11 PM, Robin Dapp wrote: Integer values and floating-point values need to be converted by fmv series instructions. So if mode1 is MODE_INT and mode2 is MODE_FLOAT, we should return false in riscv_modes_tieable

Re: [PATCH] RISC-V: Fix riscv_modes_tieable_p

2025-01-10 Thread Jeff Law
On 1/10/25 12:11 PM, Robin Dapp wrote: Integer values and floating-point values need to be converted by fmv series instructions. So if mode1 is MODE_INT and mode2 is MODE_FLOAT, we should return false in riscv_modes_tieable_p, and vice versa. I think that's on purpose because we can read and

Re: [PATCH] RISC-V: Fix riscv_modes_tieable_p

2025-01-10 Thread Robin Dapp
> Integer values and floating-point values need to be converted > by fmv series instructions. So if mode1 is MODE_INT and mode2 > is MODE_FLOAT, we should return false in riscv_modes_tieable_p, > and vice versa. I think that's on purpose because we can read and write float values from/to integer r