From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: WangYuli <wangyuli@uniontech.com>
Cc: akpm@linux-foundation.org, Liam.Howlett@oracle.com,
vbabka@suse.cz, jannh@google.com, pfalcato@suse.de,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
niecheng1@uniontech.com, guanwentao@uniontech.com,
Jun Zhan <zhanjun@uniontech.com>
Subject: Re: [PATCH] tools/testing/vma: Fix function parameter declarations for GCC 8.3 compatibility
Date: Tue, 29 Jul 2025 10:06:40 +0100 [thread overview]
Message-ID: <e7554f93-03e8-4315-acb7-a55312354485@lucifer.local> (raw)
In-Reply-To: <EFCEBE7E301589DE+20250729084700.208767-1-wangyuli@uniontech.com>
On Tue, Jul 29, 2025 at 04:47:00PM +0800, WangYuli wrote:
> The Linux kernel's minimum GCC version requirement has been bumped
> from 4.3 to 8.3, but this tool still fails to compile with GCC 8.3.
Why people keep reporting this for my VMA test series but _not_ the kernel
as a whole I don't know.
$ grep "\*);" include/linux/mm.h | wc -l
9
^--- If you use such a compiler, the kernel won't build.
So the bug is whoever is saying a version of gcc that does the below (I'll
take your word for it that this is in a normal configuraiton) is OK for the
kernel.
It's clearly not.
Oh just to underline things:
$ find include/linux -name '*.h' | xargs grep "\*);" | wc -l
1899
So y'know.
>
> Older compilers would fail if did not include parameter names in
> function declarations that contained parameter types; newer compilers
> are more lenient about this.
You're using a compiler that won't build linux. Stop it?
>
> Fix many errors like this:
> In file included from vma.c:10:
> vma_internal.h: In function ‘arch_validate_flags’:
> vma_internal.h:1218:40: error: parameter name omitted
> static inline bool arch_validate_flags(unsigned long)
> ^~~~~~~~~~~~~
> vma.c: In function ‘dummy_close’:
> vma.c:281:25: error: parameter name omitted
> static void dummy_close(struct vm_area_struct *)
> ^~~~~~~~~~~~~~~~~~~~~~~
>
> Reported-by: Jun Zhan <zhanjun@uniontech.com>
> Signed-off-by: WangYuli <wangyuli@uniontech.com>
NAK.
next prev parent reply other threads:[~2025-07-29 9:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 8:47 WangYuli
2025-07-29 9:06 ` Lorenzo Stoakes [this message]
2025-07-31 2:55 ` WangYuli
2025-07-31 10:24 ` Lorenzo Stoakes
2025-07-31 18:13 ` Vlastimil Babka
2025-08-01 5:14 ` Lorenzo Stoakes
2025-08-01 5:57 ` WangYuli
2025-08-01 8:04 ` Vlastimil Babka
2025-08-01 8:50 ` Lorenzo Stoakes
2025-08-01 9:22 ` Vlastimil Babka
2025-08-01 9:26 ` WangYuli
2025-08-01 9:33 ` Lorenzo Stoakes
2025-08-01 9:48 ` Vlastimil Babka
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=e7554f93-03e8-4315-acb7-a55312354485@lucifer.local \
--to=lorenzo.stoakes@oracle.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=guanwentao@uniontech.com \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=niecheng1@uniontech.com \
--cc=pfalcato@suse.de \
--cc=vbabka@suse.cz \
--cc=wangyuli@uniontech.com \
--cc=zhanjun@uniontech.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