From: Paolo Bonzini <pbonzini@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] tests: add gcov target
Date: Mon, 11 Jun 2012 06:56:20 +0200 [thread overview]
Message-ID: <4FD57A74.5090309@redhat.com> (raw)
In-Reply-To: <CAAu8pHuJ4dCzKOTudZdK_q=_pMo=Cv84LCFT32YC+SY5oG2WYA@mail.gmail.com>
Il 10/06/2012 20:07, Blue Swirl ha scritto:
> > > check-unit-y = tests/check-qdict$(EXESUF)
> > > +GCOV_FILES = $(SRC_PATH)/qdict.c
> >
> > Ouch, ugly. Why is it needed?
>
> Gcov needs to know both the source file and the object. Probably it
> can't get this information from the object or .gc{da,no} files.
Yes, I meant why in QEMU. In the new buildsystem all .o files match the
original hierarchy in the source tree, so it should be possible to avoid
this and get it from substitutions on the names of the .gcda files.
Paolo
next prev parent reply other threads:[~2012-06-11 4:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-10 13:04 [Qemu-devel] [PATCH 1/2] libcacard: build fixes Blue Swirl
2012-06-10 13:04 ` [Qemu-devel] [PATCH 2/2] tests: add gcov target Blue Swirl
2012-06-10 16:04 ` Paolo Bonzini
2012-06-10 18:07 ` Blue Swirl
2012-06-11 4:56 ` Paolo Bonzini [this message]
2012-06-10 16:08 ` Andreas Färber
2012-06-10 18:14 ` Blue Swirl
2012-06-10 13:32 ` [Qemu-devel] [PATCH 1/2] libcacard: build fixes Alon Levy
2012-06-10 16:10 ` Andreas Färber
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=4FD57A74.5090309@redhat.com \
--to=pbonzini@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.