public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "nimble dude" <nimble.dude@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: Re: Can gcc-4.2 be used to measure coverage on SMP platforms?
Date: Sun, 24 Aug 2008 06:46:00 -0000	[thread overview]
Message-ID: <1d7c6ac80808232301y2fcad20bya92de69adc4be776@mail.gmail.com> (raw)
In-Reply-To: <1d7c6ac80808142036k7459eb68hbebb027615cc2fcb@mail.gmail.com>

2nd try...
Would be grateful if somebody could confirm one way or the other.



On Thu, Aug 14, 2008 at 8:36 PM, nimble dude <nimble.dude@gmail.com> wrote:
> Hello,
>
>    I have a newbie question about gcov and SMP support in gcov.
>
>    I am trying to measure the coverage information of a
> multi-threaded application running on an SMP platform. I compiled the
> image with "-fprofile-arcs -ftest-coverage" and linked with -lgcov.
> All optimizations were turned off. When the coverage was observed,
> some of the counters were wrong. Sure enough, in the disassembly
> output, the incrementing of the gcov related variables was not atomic.
> Searching gcc manuals for further info on gcov did not yield any
> information. The documentation on SMP and gcov support is rather
> sparse.
>
> - Does gcc-4.2 support atomic_increment of the gcov related information?
> - If so, is there another option that needs to be specified along with "gcc"
> - Does gcc-4.3.1 support atomic_increment of gcov counters
> natively(i.e, without further flags)?
>
> I appreciate your help in advance. Please excuse if this is already
> mentioned in documentation.
>
> Thank you,
> Ram
>

  reply	other threads:[~2008-08-24  6:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-15 11:08 nimble dude
2008-08-24  6:46 ` nimble dude [this message]
2008-08-26 10:22   ` Holger Blasum

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=1d7c6ac80808232301y2fcad20bya92de69adc4be776@mail.gmail.com \
    --to=nimble.dude@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    /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).