From: Peter Oberparleiter <oberpar@linux.ibm.com>
To: Tri Vo <trong@android.com>
Cc: ghackmann@android.com, ndesaulniers@google.com,
linux-kernel@vger.kernel.org, kernel-team@android.com,
yamada.masahiro@socionext.com
Subject: Re: [PATCH v3 3/3] gcov: docs: add a note on GCC vs Clang differences
Date: Tue, 5 Mar 2019 15:07:41 +0100 [thread overview]
Message-ID: <018fe29b-bad5-e789-1fe7-73f42a90a65e@linux.ibm.com> (raw)
In-Reply-To: <20190122233749.42220-4-trong@android.com>
On 23.01.2019 00:37, Tri Vo wrote:
> Document some things of note to gcov users:
> 1. GCC gcov and Clang llvm-cov tools are not compatible.
> 2. The use of GCC vs Clang is transparent at build-time.
For completeness sake please also add something like the following to
the commit message:
Also adjust the documentation to account for the removal of config
symbol CONFIG_GCOV_FORMAT_AUTODETECT by commit 6a61b70b43c9
("gcov: remove CONFIG_GCOV_FORMAT_AUTODETECT").
>
> Signed-off-by: Tri Vo <trong@android.com>
> ---
> Documentation/dev-tools/gcov.rst | 18 ++++++++++++++----
> 1 file changed, 14 insertions(+), 4 deletions(-)
Reviewed-by: Peter Oberparleiter <oberpar@linux.ibm.com>
--
Peter Oberparleiter
Linux on Z Development - IBM Germany
next prev parent reply other threads:[~2019-03-05 14:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 23:37 [PATCH v3 0/3] gcov: add Clang support Tri Vo
2019-01-22 23:37 ` [PATCH v3 1/3] gcov: Clang: move common GCC code into gcc_base.c Tri Vo
2019-03-05 13:40 ` Peter Oberparleiter
2019-01-22 23:37 ` [PATCH v3 2/3] gcov: Clang support Tri Vo
2019-03-05 13:57 ` Peter Oberparleiter
2019-01-22 23:37 ` [PATCH v3 3/3] gcov: docs: add a note on GCC vs Clang differences Tri Vo
2019-01-22 23:50 ` Nick Desaulniers
2019-03-05 14:07 ` Peter Oberparleiter [this message]
2019-02-07 0:52 ` [PATCH v3 0/3] gcov: add Clang support Nick Desaulniers
2019-02-22 0:57 ` Nick Desaulniers
2019-03-05 14:29 ` Peter Oberparleiter
2019-03-12 4:57 ` Tri Vo
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=018fe29b-bad5-e789-1fe7-73f42a90a65e@linux.ibm.com \
--to=oberpar@linux.ibm.com \
--cc=ghackmann@android.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ndesaulniers@google.com \
--cc=trong@android.com \
--cc=yamada.masahiro@socionext.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
Powered by JetHome