[Bug middle-end/21360] [3.4/4.0/4.1 Regression] wrong result of 'if' statement with comparing of floating point with gcc.

2005-05-03 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-05-03 
15:21 ---
Confirmed.

-- 
   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever Confirmed||1
   Keywords||wrong-code
   Last reconfirmed|-00-00 00:00:00 |2005-05-03 15:21:14
   date||
Summary|wrong result of 'if'|[3.4/4.0/4.1 Regression]
   |statement with  comparing of|wrong result of 'if'
   |floating point with gcc.|statement with  comparing of
   ||floating point with gcc.
   Target Milestone|--- |3.4.4


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21360


[Bug middle-end/21360] [3.4/4.0/4.1 Regression] wrong result of 'if' statement with comparing of floating point with gcc.

2005-05-03 Thread jsm28 at gcc dot gnu dot org

--- Additional Comments From jsm28 at gcc dot gnu dot org  2005-05-03 16:33 
---
Conversion of out-of-range floating point values to integers yields undefined
behavior in both C and C++.  There is no need for it to be consistent between
compile-time and runtime conversions.

However, the ISO C decimal floating point proposals (DTR 24732 / WG14 N1107)
make it well-defined for binary as well as decimal floating-point types.  So we
do want to support well-defined semantics (namely, those in that proposal) for
both compile-time and runtime conversions, at least under a command-line option
to enable them.  I don't know whether dfp-branch has such support yet. 
Performance measurements would be needed to ascertain whether there is any
benefit to having both versions or whether we might as well just always use the
DTR 24732 semantics for these conversions (and document that we are doing so,
and seek out and eliminate any optimizations in the compiler which depend on
such conversions being undefined - a search for such optimizations being a
necessary part of the decimal floating point work anyway if not already done).


-- 
   What|Removed |Added

 CC||bje at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21360


[Bug middle-end/21360] [3.4/4.0/4.1 Regression] wrong result of 'if' statement with comparing of floating point with gcc.

2005-05-03 Thread pinskia at gcc dot gnu dot org


-- 
   What|Removed |Added

   Severity|normal  |minor


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21360