Re: Integrated: 8288594: Address possibly lossy conversions in java.base FloatToDecimal

2022-06-16 Thread Raffaello Giulietti
Ah, no, it's a P4 bug. Sorry for the noise On 2022-06-16 23:57, Raffaello Giulietti wrote: Although the conversion is mathematically sound and never lossy, this change should probably be backported to 19 as well. Greetings Raffaello On 2022-06-16 19:01, Adam Sotona wrote: On Thu, 16 Jun 20

Re: Integrated: 8288594: Address possibly lossy conversions in java.base FloatToDecimal

2022-06-16 Thread Raffaello Giulietti
Although the conversion is mathematically sound and never lossy, this change should probably be backported to 19 as well. Greetings Raffaello On 2022-06-16 19:01, Adam Sotona wrote: On Thu, 16 Jun 2022 15:26:37 GMT, Adam Sotona wrote: One new case of possibly lossy conversions recently ap

Integrated: 8288594: Address possibly lossy conversions in java.base FloatToDecimal

2022-06-16 Thread Adam Sotona
On Thu, 16 Jun 2022 15:26:37 GMT, Adam Sotona wrote: > One new case of possibly lossy conversions recently appeared in > jdk.internal.math.FloatToDecimal. > This patch avoids the warning by explicit cast from long to int. > > Please review. > > Thanks, > Adam This pull request has now been in