From: John Hubbard <jhubbard@nvidia.com>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
Nathan Chancellor <nathan@kernel.org>, Tom Rix <trix@redhat.com>,
Jason Gunthorpe <jgg@nvidia.com>,
LKML <linux-kernel@vger.kernel.org>,
clang-built-linux <llvm@lists.linux.dev>
Subject: Re: [PATCH] gen_compile_commands: fix overlooked module files
Date: Wed, 15 Jun 2022 19:04:47 -0700 [thread overview]
Message-ID: <7125b9dc-58e9-0ce3-ee84-77d5dcdfadd4@nvidia.com> (raw)
In-Reply-To: <CAK7LNARsHxH1LF8Pq70EMAYW-p1btgAVC1cJMOkXSTjW5LZuKA@mail.gmail.com>
On 6/15/22 02:23, Masahiro Yamada wrote:
>> Fixes: ecca4fea1ede4 ("gen_compile_commands: support *.o, *.a, modules.order in positional argument")
>
> This should be
>
> Fixes: 9413e7640564 ("kbuild: split the second line of *.mod into *.usyms")
>
>
> Can you update the commit log?
>
Done.
>
>> Cc: Masahiro Yamada <masahiroy@kernel.org>
>> Cc: Nick Desaulniers <ndesaulniers@google.com>
>> Signed-off-by: John Hubbard <jhubbard@nvidia.com>
>> ---
>> scripts/clang-tools/gen_compile_commands.py | 7 ++++---
>> 1 file changed, 4 insertions(+), 3 deletions(-)
>>
>> diff --git a/scripts/clang-tools/gen_compile_commands.py b/scripts/clang-tools/gen_compile_commands.py
>> index 1d1bde1fd45e..53590e886889 100755
>> --- a/scripts/clang-tools/gen_compile_commands.py
>> +++ b/scripts/clang-tools/gen_compile_commands.py
>> @@ -157,10 +157,11 @@ def cmdfiles_for_modorder(modorder):
>> if ext != '.ko':
>> sys.exit('{}: module path must end with .ko'.format(ko))
>> mod = base + '.mod'
>> - # The first line of *.mod lists the objects that compose the module.
>> + # Read from *.mod, to get a list of objects that compose the module.
>> with open(mod) as m:
>> - for obj in m.readline().split():
>> - yield to_cmdfile(obj)
>> + for line in m.readlines():
>
>
> for line in m:
>
> is simpler, (and maybe will work more efficiently).
aha, yes.
>
>
> One more note, the 'line' iterator is shadowing (overwriting)
> the outer 'line' iterator, which has been used a few lines above.
I overlooked that point, good catch.
>
> with open(modorder) as f:
> for line in f:
>
>
>
> Maybe, it is safer to use a different name for the inner iterator
> because shadowing does not work in Python.
>
>
>
>
>
>> + for obj in line.split():
>
> This loop is unneeded because each line
> contains only one word.
> .rstpip() will do.
>
>
>
> To sum up, this part can be simpler,
> for example like this:
>
> # Read from *.mod, to get a list of objects that compose the module.
> with open(mod) as m:
> for line2 in m:
> yield to_cmdfile(line2.rstrip())
>
Yes, I'll send out a v2 with all of this. Maybe "mod_line" or something
instead of "line2", but otherwise as you've recommended.
thanks,
--
John Hubbard
NVIDIA
prev parent reply other threads:[~2022-06-16 2:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 6:33 John Hubbard
2022-06-15 9:23 ` Masahiro Yamada
2022-06-16 2:04 ` John Hubbard [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=7125b9dc-58e9-0ce3-ee84-77d5dcdfadd4@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=jgg@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=trix@redhat.com \
/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
all inboxes | Powered by JetHome®