optimization/10482: Optimized and debug binaries of same application give different results.

optimization/10482: Optimized and debug binaries of same application give different results.

[Alberto.Ribon]

>Number:         10482
>Category:       optimization
>Synopsis:       Optimized and debug binaries of same application give different results.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Apr 24 16:06:01 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Alberto.Ribon@cern.ch
>Release:        gcc 3.2.2 and earlier versions (2.95.2)
>Organization:
>Environment:
Linux Red Hat 7.3
>Description:
After building the same C++ application twice,
     once using debug  -g  option
 and once with optimization ( -O  option), 
and running them at the same conditions, the results 
numerically differ while they should be exactly the same.
We verified and are confident that there are no cases of
uninitialized variables or numerical instabilities (like
nan, division by zero, etc...).
We also verified that the same exercise on Sun Solaris
system with Forte CC 5.4 compiler (and earlier verions)
instead generates the same output in the two cases.

We would like to know if this is a known feature of gcc
compiler, and what could be the cause in terms of optimizations done with the default level -O.
>How-To-Repeat:
The problem appears in a rather complicated simulation 
application for which we don't have an easy test case to
provide.
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:

Re: optimization/10482: Optimized and debug binaries of same application give different results.

[bangerth]

Synopsis: Optimized and debug binaries of same application give different results.

State-Changed-From-To: open->feedback
State-Changed-By: bangerth
State-Changed-When: Thu Apr 24 16:27:18 2003
State-Changed-Why:
    There are known bugs in gcc, but if you want us to fix any
    potential problem (or tell you that what you do is invoking
    undefined behavior and therefore not a bug in gcc), then I
    guess you will have to tell us a little more than just "it
    doesn't work". Please review
      http://gcc.gnu.org/bugs.html
    for this purpose. It explains what we need. It also explains
    a couple of typical problems.
    
    Thanks
      Wolfgang

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10482