Re: [PATCH 2/2] perf record: Add --dry-run option to check cmdline options

[David Ahern]

On 6/20/16 8:02 PM, Namhyung Kim wrote:
> On Tue, Jun 21, 2016 at 3:13 AM, Arnaldo Carvalho de Melo
> <acme@xxxxxxxxxx> 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

That sounds more reasonable to me than 'perf cc'.