From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1754071AbcFUCDB (ORCPT <rfc822;w@1wt.eu>);
	Mon, 20 Jun 2016 22:03:01 -0400
Received: from mail-it0-f66.google.com ([209.85.214.66]:34894 "EHLO
	mail-it0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1753408AbcFUCC7 (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Mon, 20 Jun 2016 22:02:59 -0400
MIME-Version: 1.0
In-Reply-To: <20160620181343.GA3602@kernel.org>
References: <1466064161-48553-1-git-send-email-wangnan0@huawei.com>
 <1466064161-48553-3-git-send-email-wangnan0@huawei.com> <20160616164815.GE13337@kernel.org>
 <57676309.8000907@huawei.com> <20160620143818.GA3050@redhat.com>
 <20160620162208.GA67352@ast-mbp.thefacebook.com> <20160620181343.GA3602@kernel.org>
From: Namhyung Kim <namhyung@gmail.com>
Date: Tue, 21 Jun 2016 11:02:58 +0900
X-Google-Sender-Auth: 5Eo2PC0ahm3ySI01s_VHGPlLR_k
Message-ID: <CADWwUUay9GnMwcQnxC6tnA8zVd1n0SnBiyCbUqb0Lz_Wd7KTzA@mail.gmail.com>
Subject: Re: [PATCH 2/2] perf record: Add --dry-run option to check cmdline options
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
        Arnaldo Carvalho de Melo <acme@redhat.com>,
        "Wangnan (F)" <wangnan0@huawei.com>,
        LKML <linux-kernel@vger.kernel.org>, pi3orama@163.com,
        David Ahern <dsahern@gmail.com>, Namhyung Kim <namhyung@gmail.com>,
        Alexei Starovoitov <ast@kernel.org>, Jiri Olsa <jolsa@kernel.org>
Content-Type: text/plain; charset=UTF-8
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Tue, Jun 21, 2016 at 3:13 AM, Arnaldo Carvalho de Melo
<acme@kernel.org> wrote:
> Em Mon, Jun 20, 2016 at 09:22:11AM -0700, Alexei Starovoitov escreveu:
>> On Mon, Jun 20, 2016 at 11:38:18AM -0300, Arnaldo Carvalho de Melo wrote:
>> > Doing:
>
>> >     perf bcc -c foo.c
>
>> > Looks so much simpler and similar to an existing compile source code
>> > into object file workflow (gcc's, any C compiler) that I think it would
>> > fit in the workflow being discussed really nicely.
>
>> I'm hopeful that eventually we'll be able merge iovisor/bcc project
>> with perf, so would be good to reserve 'perf bcc' command for that
>> future use. Also picking a different name for compiling would be less
>> confusing to users who already familiar with bcc. Instead we can use:
>> perf bpfcc foo.c -o foo.o
>> perf cc foo.c
>
> 'perf cc' seems sensible, and has the added bonus of being one letter
> shorter :-)
>
> - Arnaldo
>
>> perf compile foo.c

What about this?

perf bpf --compile foo.c   or,
perf bpf --cc foo.c

Thanks,
Namhyung