Re: *Ping*: [PATCH] PR fortran/96711 - ICE on NINT() Function

2020-09-07 Thread Harald Anlauf
Hi Thomas, thanks for the review! > Regarding the patch: Could you change the test caes into a > run-time test and check for the results both for compile-time > simplification and evaluation at run-time? Just to make sure that > fold_convert wasn't trying to tell us something that convert doesn'

Re: *Ping*: [PATCH] PR fortran/96711 - ICE on NINT() Function

2020-09-06 Thread Thomas Koenig via Gcc-patches
Hi Harald, *ping* I don't really know about the convert vs. fold_convert issue either, but if it works, it works. Regarding the patch: Could you change the test caes into a run-time test and check for the results both for compile-time simplification and evaluation at run-time? Just to make s

*Ping*: [PATCH] PR fortran/96711 - ICE on NINT() Function

2020-09-03 Thread Harald Anlauf
*ping* > Gesendet: Montag, 24. August 2020 um 23:08 Uhr > Von: "Harald Anlauf" > An: "fortran" , "gcc-patches" > Betreff: [PATCH] PR fortran/96711 - ICE on NINT() Function > > When rounding a real to integer(16) an ICE happened due to an unhandled

[PATCH] PR fortran/96711 - ICE on NINT() Function

2020-08-24 Thread Harald Anlauf
When rounding a real to integer(16) an ICE happened due to an unhandled case in build_round_expr. The attached patch add a special case for this. I had to change a fold_convert to a convert (which seems to be frontend specific stuff), otherwise I would get errors from the generated GIMPLE. Does a