linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>
Subject: Re: PPC64 TOC. warnings
Date: Sat, 4 Feb 2023 17:35:54 -0800	[thread overview]
Message-ID: <4e96046c-96f8-d5ae-3143-00a0bba6b9b9@infradead.org> (raw)
In-Reply-To: <CAK7LNAQ2==FuLS9P3xqHocd_+4SxkP-Y45F038Y0o9SYwPR6SA@mail.gmail.com>



On 2/4/23 09:40, Masahiro Yamada wrote:
> On Sun, Feb 5, 2023 at 2:30 AM Randy Dunlap <rdunlap@infradead.org> wrote:
>>
>> Hi,
>>
>> I'm seeing thousands of these warnings:
>> (gcc 12.2.0)
>>
>>
>> ./include/generated/autoksyms.h:7:9: warning: ISO C99 requires whitespace after the macro name
>>     7 | #define __KSYM_TOC. 1
>>       |         ^~~~~~~~~~
>>
>> In file included from ../include/asm-generic/export.h:57,
>>                  from ./arch/powerpc/include/generated/asm/export.h:1,
>>                  from ../arch/powerpc/kernel/misc.S:17:
>> ./include/generated/autoksyms.h:7:9: warning: missing whitespace after the macro name
>>     7 | #define __KSYM_TOC. 1
>>       |         ^~~~~~~~~~
>>
>>
>> Can anything be done about them?
>>
>> Thanks.
>> --
>> ~Randy
> 
> 
> 
> Hmm, I just thought this issue was fixed by
> commit 29500f15b54b63ad0ea60b58e85144262bd24df2
> 
> 
> 
> Does this happen only for GCC 12?
> 
> Does the following patch fix the issue?
> (I did not test it.)
> 
> 

I have been running build tests all day (have probably done around 500 builds)
and I'm not seeing the build problem now. I don't know why not or what changed.

I have not applied the patch below. I'm just trying to reproduce the problem
and cannot do so. (Bad me: I had 3 build failures earlier but I didn't save the
failing .config files! I didn't think that it would be so difficult to reproduce.)

Thanks for your help.

> 
> 
> 
> diff --git a/scripts/gen_autoksyms.sh b/scripts/gen_autoksyms.sh
> index 12bcfae940ee..70d4ab3621f6 100755
> --- a/scripts/gen_autoksyms.sh
> +++ b/scripts/gen_autoksyms.sh
> @@ -54,7 +54,7 @@ EOT
>  } | sed -e 's/ /\n/g' | sed -n -e '/^$/!p' |
>  # Remove the dot prefix for ppc64; symbol names with a dot (.) hold entry
>  # point addresses.
> -sed -e 's/^\.//' |
> +sed -e 's/^\.//g' |
>  sort -u |
>  # Ignore __this_module. It's not an exported symbol, and will be resolved
>  # when the final .ko's are linked.


-- 
~Randy

      reply	other threads:[~2023-02-05  1:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-04 17:30 PPC64 TOC. warnings Randy Dunlap
2023-02-04 17:40 ` Masahiro Yamada
2023-02-05  1:35   ` Randy Dunlap [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=4e96046c-96f8-d5ae-3143-00a0bba6b9b9@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=masahiroy@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;
as well as URLs for NNTP newsgroup(s).