From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A8033C43387 for ; Mon, 14 Jan 2019 21:53:29 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 6F3C320657 for ; Mon, 14 Jan 2019 21:53:29 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=android.com header.i=@android.com header.b="IqUekfLQ" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726808AbfANVx2 (ORCPT ); Mon, 14 Jan 2019 16:53:28 -0500 Received: from mail-ot1-f66.google.com ([209.85.210.66]:42843 "EHLO mail-ot1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726618AbfANVx1 (ORCPT ); Mon, 14 Jan 2019 16:53:27 -0500 Received: by mail-ot1-f66.google.com with SMTP id v23so575064otk.9 for ; Mon, 14 Jan 2019 13:53:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=android.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Q3kce2bWKDtxbTxAqm3XjUoAdIiL+VPsVQKmew7W5hY=; b=IqUekfLQGzLM3++skZUsB8ff7gjAy7Q6vGoOngGw5aPFDTp2ParzJG4Z6Wc61FLiYB Ppfq28sXEBeaFXj8qf442M3nh8CZu7erIGiuFKwvQYDgQZcXASFqeUJ4JEVKTkyQSekW IEg9WxBGnB0vHuxT61uA7OnepXZ2JPfUBBdC3QI0md/DpEo7QNK5hDlURJWVfsTHecq3 BXSvbULD2SYzMEzB9h4WXtHtRgbQO3LZgYd2khYWCYNqIFiIiztc+m4v7KJnd8LCcCbL viYrVei9/fJTJ8SBz+CkWzw42Vq1dZ+1xczoobfnsJihRDylNL9lX+rwmKXMNpU6E6Bx vF+w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Q3kce2bWKDtxbTxAqm3XjUoAdIiL+VPsVQKmew7W5hY=; b=hguIQDko27Ma7q4BaD8U68xRpnBDBRPVvK0EOw06LLTqPw90gyfuVrCqzPdqkW4FGw KBYvx5DLzG3P8cnSevjC+gEzXi5RtcA/FLUzEcykNnqJ9WHIjGqHqGZQZFDaerlPUiIu d199JIEQmPYhUB3mZ6nxtx+WYBVfKxUDeDubTAjkRgRdlSgUK0YkQqw9ADxHKZPja/BT Z2I47/KwCV9hQhbsMiku+JylXrO4A+njf/0Jv8ZIcLbHL3YzL/3QaxtwzjpUkZxc3t5P LoCj69DtJ2q5lsB/0QohCWGh1n0F/xSln+MzSO8gdDVdMKHamGr/us7yBrrI55sD+fJ8 gIxA== X-Gm-Message-State: AJcUukfSGYkd3FQAiV0hTixQ+PhqWdny/dBGeUE+qTKPf9CrHaafkvso XEuEPySb+m29RmhO9WUhRqGtJws9CaXLO/EkFBpOsQ== X-Google-Smtp-Source: ALg8bN7MJsHEjNoqj900QZ+WmNE+zJDnzZpVLMg487Lrm6+iUgi189CT7MPcIgz3yqqt3rXsYax7ZNSshApnndm/zTQ= X-Received: by 2002:a9d:17c6:: with SMTP id j64mr357521otj.357.1547502806818; Mon, 14 Jan 2019 13:53:26 -0800 (PST) MIME-Version: 1.0 References: <20190114210426.177543-1-trong@android.com> In-Reply-To: From: Tri Vo Date: Mon, 14 Jan 2019 13:53:16 -0800 Message-ID: Subject: Re: [PATCH 0/4] gcov: add Clang support To: Nick Desaulniers Cc: oberpar@linux.ibm.com, Greg Hackmann , LKML , kernel-team@android.com Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jan 14, 2019 at 1:33 PM Nick Desaulniers wrote: > > On Mon, Jan 14, 2019 at 1:04 PM Tri Vo 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? Yes, .gcda files generated by a Clang-built kernel could only be parsed by llvm-cov, but not gcc gcov (at least in my local tests). llvm-cov documentation also indicates that GCC and LLVM gcov tools are not necessarily compatible. "[llvm-cov] is compatible with the gcov tool from version 4.2 of GCC and may also be compatible with some later versions of gcov." https://llvm.org/docs/CommandGuide/llvm-cov.html