Jakub Jelinek <[EMAIL PROTECTED]> wrote: ... > We already special case e.g. 0x0000.80000000.00000000 (pseudo denormal > with implicit bit set), so I guess we can also special case this other > misdesigned FP type.
Great! ... > That said, programs that pass arbitrary bit patterns read from an insecure > source to *printf and other functions are definitely > broken as floating point numbers, they can hit signalling NaNs etc. They aren't necessarily broken. They should be able to deal with an sNaN via a SIGFPE handler. With your change, they won't have to handle SIGSEGV. Thank you!
