From: Wei Liu <wei.liu2@citrix.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Tim Deegan <tim@xen.org>, Jan Beulich <JBeulich@suse.com>,
Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH 3/4] xen: fix gcov compilation
Date: Tue, 30 Aug 2016 14:30:47 +0100 [thread overview]
Message-ID: <20160830133047.GL8502@citrix.com> (raw)
In-Reply-To: <22469.33442.585763.359592@mariner.uk.xensource.com>
On Tue, Aug 30, 2016 at 01:57:06PM +0100, Ian Jackson wrote:
> Wei Liu writes ("[PATCH 3/4] xen: fix gcov compilation"):
> > Currently enabling gcov in hypervisor won't build because although
> > 26c9d03d ("gcov: Adding support for coverage information") claimed that
> > %.init.o files were excluded from applying compilation options, it was
> > in fact not true.
> >
> > Fix that by filtering out the options correctly. Due to the dependency
> > of stub.o in x86 EFI build can't be eliminated easily and we prefer a
> > generalised method going forward, we introduce nogov-y to explicitly
> ^
> > mark objects that don't need to build with gcov support.
>
> And I'm afraid the second sentence there is not comprehensible. It
> seesm to be "Due to X, Y" but I can't quite figure out which parts of
> the sentence are X and which are Y.
>
Let's rewrite it as such:
Due to 1) the dependency of stub.o in x86 EFI build can't be eliminated
easily and 2) we prefer a generalised method going forward, we introduce
nogov-y to explicitly.
Is this clearer?
> I'm not unhappy with the approach in the Makefile, though.
>
> Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-08-30 13:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-30 12:01 [PATCH 0/4] Fix gcov build Wei Liu
2016-08-30 12:01 ` [PATCH 1/4] arm: acpi/boot.c is only used during initialisation Wei Liu
2016-08-31 13:25 ` Julien Grall
2016-08-31 13:45 ` Wei Liu
2016-08-31 13:54 ` Julien Grall
2016-08-30 12:01 ` [PATCH 2/4] arm64: use "b" to branch to start_xen Wei Liu
2016-08-30 13:28 ` Konrad Rzeszutek Wilk
2016-08-31 13:40 ` Julien Grall
2016-08-30 12:01 ` [PATCH 3/4] xen: fix gcov compilation Wei Liu
2016-08-30 12:57 ` Ian Jackson
2016-08-30 12:59 ` Jan Beulich
2016-08-30 13:30 ` Wei Liu [this message]
2016-08-30 12:01 ` [PATCH 4/4] xen: add a gcov Kconfig option Wei Liu
2016-08-30 12:56 ` Jan Beulich
2016-08-30 13:06 ` Wei Liu
2016-08-30 16:49 ` Doug Goldstein
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=20160830133047.GL8502@citrix.com \
--to=wei.liu2@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=xen-devel@lists.xenproject.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).