Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
References: <20190114210426.177543-1-trong@android.com>
In-Reply-To: <20190114210426.177543-1-trong@android.com>
From:   Nick Desaulniers <ndesaulniers@google.com>
Date:   Mon, 14 Jan 2019 13:32:52 -0800
Message-ID: <CAKwvOdkoN1myuDM1OFga+v30LQ9pV5VD9J_KCJN1Z7AY+kaXxQ@mail.gmail.com>
Subject: Re: [PATCH 0/4] gcov: add Clang support
To:     Tri Vo <trong@android.com>
Cc:     oberpar@linux.ibm.com, ghackmann@android.com,
        LKML <linux-kernel@vger.kernel.org>, kernel-team@android.com
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Mon, Jan 14, 2019 at 1:04 PM Tri Vo <trong@android.com> wrote:
>
> 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

Thanks for sending Tri!  Doesn't the output format require llvm-cov, or no?
-- 
Thanks,
~Nick Desaulniers