------- Comment #8 from rguenth at gcc dot gnu dot org 2008-04-14 11:06 ------- I propose that we do the following:
- add a warning to the C/C++ frontends that isinf (x) CMP isinf (y) is only well-defined for !isinf (x) && !isinf (y). this doesn't result in a runtime penalty and informs people about the possible problem in their code (it is non-portable). A different workaround would be to canonicalize the return value of isinf to bool. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35509
