From: Nathan Sidwell <nathan@codesourcery.com>
To: Lothar Werzinger <lothar@xcerla.com>
Cc: gcc@gcc.gnu.org
Subject: Re: different code behaviour with -fprofile-arcs -ftest-coverage
Date: Fri, 01 Aug 2003 09:52:00 -0000 [thread overview]
Message-ID: <3F2A260D.1010406@codesourcery.com> (raw)
In-Reply-To: <1059693738.15674.50.camel@localhost>
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
parent reply other threads:[~2003-08-01 8:34 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1059693738.15674.50.camel@localhost>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F2A260D.1010406@codesourcery.com \
--to=nathan@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=lothar@xcerla.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).