From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@gmail.com>,
QEMU <qemu-devel@nongnu.org>
Subject: Re: Deprecating --enable-gprof?
Date: Fri, 18 Sep 2020 15:27:27 +0100 [thread overview]
Message-ID: <20200918142727.GM1628512@redhat.com> (raw)
In-Reply-To: <CAFEAcA8CHK49OChJ9V6g2xj=_9UZLOzy5My0KViWmSEp5Q8_Qg@mail.gmail.com>
On Fri, Sep 18, 2020 at 03:19:00PM +0100, Peter Maydell wrote:
> On Fri, 18 Sep 2020 at 14:27, Marc-André Lureau
> <marcandre.lureau@gmail.com> wrote:
> >
> > Hi
> >
> > configure has --enable-gprof since its creation, but is it actually being used, or is it sporadic enough that we could deprecate it?
>
> This reminds me (because I can never keep gprof and gcov straight
> in my head :-)) that now the meson build has landed we should
> probably insist on gcov/gcovr being at least version 4.1, because
> older versions don't correctly handle out of tree builds:
> https://lists.gnu.org/archive/html/qemu-devel/2020-06/msg05823.html
I think we might not need todo anything at this point. --enable-gcov
just delegates to meson by passing "-Db_coverage=true" to meson.
We still have a coverage-summary.sh script that is run in Travis, but
I'm not sure if that's obsolete or not
If we were using meson/ninja directly we'd just do "meson coverage-html"
to generate a report:
https://mesonbuild.com/howtox.html#producing-a-coverage-report
and the resulting file could be published from CI as an artifact.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2020-09-18 14:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 13:25 Deprecating --enable-gprof? Marc-André Lureau
2020-09-18 13:36 ` Daniel P. Berrangé
2020-09-18 14:19 ` Peter Maydell
2020-09-18 14:27 ` Daniel P. Berrangé [this message]
2020-09-19 6:10 ` Paolo Bonzini
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=20200918142727.GM1628512@redhat.com \
--to=berrange@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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 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 NNTP newsgroup(s).