From: Tri Vo <trong@android.com>
To: oberpar@linux.ibm.com
Cc: ghackmann@android.com, ndesaulniers@google.com,
linux-kernel@vger.kernel.org, kernel-team@android.com,
Tri Vo <trong@android.com>
Subject: [PATCH 0/4] gcov: add Clang support
Date: Mon, 14 Jan 2019 13:04:22 -0800 [thread overview]
Message-ID: <20190114210426.177543-1-trong@android.com> (raw)
This patch series adds Clang supoprt for gcov.
Patch 1 refactors existing code in preparation for Clang support. Patches
2-3 implement necessary LLVM runtime hooks and gcov kernel interfaces.
Patch 4 simplifies config selection.
Greg Hackmann (2):
gcov: clang: move common gcc code into gcc_base.c
gcov: clang support
Nick Desaulniers (1):
gcov: clang: link/unlink profiling data set.
Tri Vo (1):
gcov: clang: pick GCC vs Clang format depending on compiler
kernel/gcov/Kconfig | 9 +
kernel/gcov/Makefile | 5 +-
kernel/gcov/base.c | 78 +-----
kernel/gcov/clang.c | 554 +++++++++++++++++++++++++++++++++++++++++
kernel/gcov/gcc_base.c | 79 ++++++
kernel/gcov/gcov.h | 3 +
6 files changed, 650 insertions(+), 78 deletions(-)
create mode 100644 kernel/gcov/clang.c
create mode 100644 kernel/gcov/gcc_base.c
--
2.20.1.97.g81188d93c3-goog
next reply other threads:[~2019-01-14 21:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 21:04 Tri Vo [this message]
2019-01-14 21:04 ` [PATCH 1/4] gcov: clang: move common gcc code into gcc_base.c Tri Vo
2019-01-16 15:32 ` Peter Oberparleiter
2019-01-14 21:04 ` [PATCH 2/4] gcov: clang support Tri Vo
2019-01-16 16:06 ` Peter Oberparleiter
2019-01-14 21:04 ` [PATCH 3/4] gcov: clang: link/unlink profiling data set Tri Vo
2019-01-16 16:14 ` Peter Oberparleiter
2019-01-14 21:04 ` [PATCH 4/4] gcov: clang: pick GCC vs Clang format depending on compiler Tri Vo
2019-01-14 21:11 ` Nick Desaulniers
2019-01-15 1:24 ` Masahiro Yamada
2019-01-15 17:52 ` Tri Vo
2019-01-14 21:32 ` [PATCH 0/4] gcov: add Clang support Nick Desaulniers
2019-01-14 21:53 ` Tri Vo
2019-01-14 22:00 ` Nick Desaulniers
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=20190114210426.177543-1-trong@android.com \
--to=trong@android.com \
--cc=ghackmann@android.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ndesaulniers@google.com \
--cc=oberpar@linux.ibm.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 NNTP newsgroup(s).