Hi! I am planning to commit the following patch (with a suitable ChangeLog entry)
--- ../_clean/gcc/fortran/invoke.texi 2019-01-30 16:54:38.000000000 +0100 +++ gcc/fortran/invoke.texi 2019-02-01 11:52:01.000000000 +0100 @@ -1203,6 +1203,12 @@ The first three exceptions (@samp{invali has provisions for dealing with these exceptions, enabling traps for these three exceptions is probably a good idea. +If the option is used more than once in the command line, the lists will +be joined: '@code{ffpe-trap=}@var{list1} @code{ffpe-trap=}@var{list2}' +is equivalent to @code{ffpe-trap=}@var{list1,list2}. + +Note that once enabled an exception cannot be disabled (no negative form). + Many, if not most, floating point operations incur loss of precision due to rounding, and hence the @code{ffpe-trap=inexact} is likely to be uninteresting in practice. @@ -1218,6 +1224,9 @@ of the following exceptions: @samp{inval @samp{underflow}, @samp{inexact} and @samp{denormal}. (See @option{-ffpe-trap} for a description of the exceptions.) +If the option is used more than once in the command line, only the +last one will be used. + By default, a summary for all exceptions but @samp{inexact} is shown. @item -fno-backtrace then to close the PR as WONTFIX. Is it OK? TIA Dominique