[Bug tree-optimization/110335] int converted to double should be considered non-nan and non-nan*non-nan is still non-nan

[pinskia at gcc dot gnu.org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110335

--- Comment #2 from Drea Pinski <pinskia at gcc dot gnu.org> ---
So GCC handles h just fine since GCC 16.

h1 is not.

For h1 we have:
  # RANGE [frange] double [-Inf, +Inf]
  doubleD.42 dto_1(D) = dtoD.2999;
  # RANGE [frange] double [-Inf, +Inf]
  doubleD.42 n_2(D) = nD.3000;


  damt_3 = dto_1(D) * n_2(D);

Which seems like we don't get a range on damt_3 not being NaNs.