different code behaviour with -fprofile-arcs -ftest-coverage

[Nathan Sidwell]

Lothar Werzinger wrote:

> Here's the output of this code fragment:
>   without code coverage:
> unsigned long 
> 5 5 0 1 0 1 1 0 
> double 
> 5 5 0 1 0 1 1 0 
> 
>   with code coverage:
> unsigned long 
> 5 5 0 1 0 1 1 0 
> double 
> 5 5 0 1 0 1 0 1 
> 
> 
> How can the comparison operators claim the value is both, the same and
> different? And why does it affect only the double type?
> 
> Has anyone an idea how this can happen? Is there a way to get correct
> results even with code coverage analysis?
this is most likely a gcc bug. Please file a bug report by following
instructions on the gcc web page.

nathan

-- 
Nathan Sidwell    ::   http://www.codesourcery.com   ::     CodeSourcery LLC
          The voices in my head said this was stupid too
nathan@codesourcery.com    ::     http://www.planetfall.pwp.blueyonder.co.uk