[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <81864464-8cd1-8afe-ed57-c04b1b22a35b@arm.com>
Date: Thu, 1 Sep 2022 10:41:46 +0530
From: Anshuman Khandual <anshuman.khandual@....com>
To: Stephen Rothwell <sfr@...b.auug.org.au>,
Arnaldo Carvalho de Melo <arnaldo.melo@...il.com>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the perf tree
Hello Stephen,
This seems to be the same problem as pointed by ACME on the patch series [1].
Could this be a compiler false positive ? Because the new code block is exact
same like the existing one. This warning seems to only occurs on powerpc64el
platform, but not on others.
[1] https://lore.kernel.org/lkml/Yw59CkHUVbfrHdkh@kernel.org/
- Anshuman
On 8/31/22 04:04, Stephen Rothwell wrote:
> Hi all,
>
> After merging the perf tree, today's linux-next build (native perf)
> failed like this:
>
> In file included from /usr/include/stdio.h:866,
> from /home/sfr/next/next/tools/perf/util/branch.h:9,
> from util/branch.c:2:
> In function 'fprintf',
> inlined from 'branch_type_stat_display' at util/branch.c:152:4:
> /usr/include/powerpc64le-linux-gnu/bits/stdio2.h:105:10: error: '%8s' directive argument is null [-Werror=format-overflow=]
> 105 | return __fprintf_chk (__stream, __USE_FORTIFY_LEVEL - 1, __fmt,
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 106 | __va_arg_pack ());
> | ~~~~~~~~~~~~~~~~~
> cc1: all warnings being treated as errors
>
> Presumably caused by commit
>
> 9781e500dcb8 ("perf branch: Extend branch type classification")
>
> "native" here is PowerPC64 LE.
> $ gcc --version
> gcc (Debian 11.2.0-10) 11.2.0
>
> I have used the perf tree from next-20220830 for today.
>
Powered by blists - more mailing lists