Netdev List
 help / color / mirror / Atom feed
From: Yonghong Song <yhs@fb.com>
To: Daniel Borkmann <daniel@iogearbox.net>,
	Martin KaFai Lau <kafai@fb.com>, <netdev@vger.kernel.org>
Cc: Alexei Starovoitov <ast@fb.com>, <kernel-team@fb.com>
Subject: Re: [PATCH bpf] bpf: Use option "help" in the llvm-objcopy test
Date: Tue, 24 Jul 2018 17:30:23 -0700	[thread overview]
Message-ID: <537c2d77-a10d-e108-e6a3-75c5c7a4b954@fb.com> (raw)
In-Reply-To: <34e16aab-db8b-ef38-4c56-6bbf6e81f673@iogearbox.net>



On 7/20/18 1:37 AM, Daniel Borkmann wrote:
> On 07/20/2018 07:34 AM, Martin KaFai Lau wrote:
>> I noticed the "--version" option of the llvm-objcopy command has recently
>> disappeared from the master llvm branch.  It is currently used as a BTF
>> support test in tools/testing/selftests/bpf/Makefile.
>>
>> This patch replaces it with "--help" which should be
>> less error prone in the future.
>>
>> Fixes: c0fa1b6c3efc ("bpf: btf: Add BTF tests")
>> Signed-off-by: Martin KaFai Lau <kafai@fb.com>
> 
> Looks good, ran into the same recently as well from llvm git. Wondering whether
> the "--version" removal there was by accident or on purpose. In any case, applied

The option "--version" seems removed by accident.
On 6.0.0, the option handling is done by llvm.
      static cl::opt<std::string>
              OutputFormat("O", cl::desc("Set output format to one of the
                           following:"
                           "\n\tbinary"));
      cl::ParseCommandLineOptions(argc, argv, "llvm objcopy utility\n");
That is, the options are defined through llvm option handling system and
option "--version" is handled by llvm automatically.

In 7.0.0, llvm-objcopy tries to handle the options itself. 
Unfortunately, it did not define "version" option in its option file, so
"llvm-objcopy --version" won't work any more.

I will raise a bug or fix the issue properly.

> to bpf tree, thanks! If we make another change to the Makefile in near future,
> we should also make a comment there that the llvm-objcopy is used by pahole -J
> internally to make it a bit more clear in case someone is wondering why it's not
> used in the Makefile itself.
> 
> Thanks,
> Daniel
> 

      reply	other threads:[~2018-07-25  1:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-20  5:34 [PATCH bpf] bpf: Use option "help" in the llvm-objcopy test Martin KaFai Lau
2018-07-20  8:37 ` Daniel Borkmann
2018-07-25  0:30   ` Yonghong Song [this message]

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=537c2d77-a10d-e108-e6a3-75c5c7a4b954@fb.com \
    --to=yhs@fb.com \
    --cc=ast@fb.com \
    --cc=daniel@iogearbox.net \
    --cc=kafai@fb.com \
    --cc=kernel-team@fb.com \
    --cc=netdev@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox