https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82207
--- Comment #7 from Steve Kargl <sgk at troutmask dot apl.washington.edu> --- On Tue, Jan 23, 2018 at 08:53:36PM +0000, guez at lmd dot ens.fr wrote: > > This behaviour of gfortran is a problem because it prevents the use of qnan as > a normal missing value and the debugging option at the same time. > AFAICT, gfortran make no distinction between qNaN and sNaN. If you use -ffpe-trap=invalid, gfortran will abort. Patches to honor qNaN vs sNaN are welcomed.
