Re: Reporting bugs: there is nothing to gain in frustrating reporters

[Andrew Pinski <pinskia at physics dot uc dot edu>]

> Thank you very much. Note that you're "re-closed" is incorrect because
> a SUSPENDED bug is still open (but suspended); look at bugzilla's
> documentation... This is important for the above reasons and also
> because users will be able to see this bug when searching on bugzilla
> (let's hope that this will reduce future duplicates).

Note this bug was not marked as invalid by some random bug master
but by RTH, one of the core GCC developers, and there was a reason
why it was because it is a bug which cannot fixed so easily.  Maybe
will not fix would be better but since at the time, we using gnats
which did not have "will not fix", it got marked as invalid instead.
Also note the description of this "bug" is on the non-bug part of
the bug reporting page and we still get dups.  In fact we get dups
of other real non-bugs dealing with C/C++ aliasing rule violation
so we will still get bugs for this one too.

Quote from bugs.html:

Problems with floating point numbers - the most often reported non-bug.


In a number of cases, GCC appears to perform floating point 
computations incorrectly. For example, the C++ program

#include <iostream>

int main()
{
  double a = 0.5;
  double b = 0.01;
  std::cout << (int)(a / b) << std::endl;
  return 0;
}



might print 50 on some systems and optimization levels, and 49 on 
others.


This is the result of rounding: The computer cannot represent all real 
numbers exactly, so it has to use approximations. When computing with 
approximation, the computer needs to round to the nearest representable 
number.


This is not a bug in the compiler, but an inherent limitation of the 
floating point types. Please study this paper for more information.

-- Pinski