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,
yamada.masahiro@socionext.com, Tri Vo <trong@android.com>
Subject: [PATCH v3 0/3] gcov: add Clang support
Date: Tue, 22 Jan 2019 15:37:46 -0800 [thread overview]
Message-ID: <20190122233749.42220-1-trong@android.com> (raw)
This patch series adds Clang supoprt for gcov.
Patch 1 refactors existing code in preparation for Clang support.
Patch 2 implements necessary LLVM runtime hooks and gcov kernel interfaces.
Patch 3 updates documentation.
Greg Hackmann (2):
gcov: Clang: move common GCC code into gcc_base.c
gcov: Clang support
Tri Vo (1):
gcov: docs: add a note on GCC vs Clang differences
Documentation/dev-tools/gcov.rst | 18 +-
kernel/gcov/Kconfig | 3 +-
kernel/gcov/Makefile | 5 +-
kernel/gcov/base.c | 84 +----
kernel/gcov/clang.c | 555 +++++++++++++++++++++++++++++++
kernel/gcov/gcc_base.c | 86 +++++
kernel/gcov/gcov.h | 3 +
7 files changed, 665 insertions(+), 89 deletions(-)
create mode 100644 kernel/gcov/clang.c
create mode 100644 kernel/gcov/gcc_base.c
v2:
- Reorganized config dependencies, as per Masahiro.
v3:
- Squashed patches 2-4 of v2, as per Nick, Masahiro, and Peter.
Addressed comments by Peter:
- Moved __gcov_exit() to gcc_base.c
- Added missing header to gcc_base.c
- Removed unnecessary boundary checks in gcov_info_add().
- Changed counters' allocation to use vmalloc().
- Added check for failed allocation of filename.
- Changed list_for_each_entry_safe to list_for_each_entry when traversing
without modifying.
- Updated Documentation/dev-tools/gcov.rst
--
2.20.1.321.g9e740568ce-goog
next reply other threads:[~2019-01-22 23:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 23:37 Tri Vo [this message]
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
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=20190122233749.42220-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 \
--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 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.