From: Holger Blasum <hbl@sysgo.com>
To: nimble dude <nimble.dude@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Can gcc-4.2 be used to measure coverage on SMP platforms?
Date: Tue, 26 Aug 2008 10:22:00 -0000 [thread overview]
Message-ID: <20080825210326.GA5312@koretsu> (raw)
In-Reply-To: <1d7c6ac80808232301y2fcad20bya92de69adc4be776@mail.gmail.com>
On Sat, Aug 23, 2008 at 11:01:29PM -0700, nimble dude wrote:
> > 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"
> 2nd try...
> Would be grateful if somebody could confirm one way or the other.
Concerning gcc version 3:
"Especially our implementation does not support threading
and is not able to cope very well with constructors, destructors
and dynamically loaded objects yet." J Hubicka 2005, Profile driven
optimisations in GCC, in: Proceedings of the GCC Developers' Summit,
June 21-24, 2005, Ottawa, Canada, pp. 107-124,
http://www.gccsummit.org/2005/2005-GCC-Summit-Proceedings.pdf
But that was in 2005, for gcc-4.x you may want to double-check with the
lcov list https://lists.sourceforge.net/lists/listinfo/ltp-coverage that
also has gcov users. (Note: if you do not want exact numbers
but just the conservative information whether something is covered at
all or not you might make use of the non-SMP code instrumentation
(please carefully observe the generated code on your platform) - one
of (possibly more) preparations (eg avoid counter overflow) would
be to modify the instrumentation in find_spanning_tree.)
> > - Does gcc-4.3.1 support atomic_increment of gcov counters
> > natively(i.e, without further flags)?
Is there any indication that atomic_increment of gcov counters
is supported non-natively, that is with further flags?
--
Holger Blasum
SYSGO AG Office Mainz
Web: http://www.sysgo.com
prev parent reply other threads:[~2008-08-26 6:19 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
2008-08-26 10:22 ` Holger Blasum [this message]
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=20080825210326.GA5312@koretsu \
--to=hbl@sysgo.com \
--cc=gcc-help@gcc.gnu.org \
--cc=nimble.dude@gmail.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).