From: Vineet Gupta <vgupta@kernel.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>,
open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org,
Linux Regressions <regressions@lists.linux.dev>,
linux-mm <linux-mm@kvack.org>,
linux-snps-arc@lists.infradead.org
Cc: Anders Roxell <anders.roxell@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
Andrew Morton <akpm@linux-foundation.org>,
vgupta@kernel.org
Subject: Re: next: arc: defconfig - gcc-9 - mmu-arcv2.h:82:2: error: implicit declaration of function 'write_aux_reg' [-Werror=implicit-function-declaration]
Date: Wed, 27 Mar 2024 22:46:20 -0700 [thread overview]
Message-ID: <d22054a8-76d3-4ae2-9e20-38a7a8ce902d@kernel.org> (raw)
In-Reply-To: <CA+G9fYu49=6_L6r8hdagZHUSGk+JfjioFaqh+kRaxhce84Q5Kw@mail.gmail.com>
On 3/25/24 23:39, Naresh Kamboju wrote:
> The following arc defconfig build warnings / errors noticed on today's
> Linux next-20240326 tag.
>
> Regressions:
> * arc - defconfig - gcc-9 build failed.
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> Build log:
> ---------
> arch/arc/kernel/ptrace.c:342:16: warning: no previous prototype for
> 'syscall_trace_enter' [-Wmissing-prototypes]
> 342 | asmlinkage int syscall_trace_enter(struct pt_regs *regs)
> | ^~~~~~~~~~~~~~~~~~~
> arch/arc/kernel/kprobes.c:193:15: warning: no previous prototype for
> 'arc_kprobe_handler' [-Wmissing-prototypes]
> 193 | int __kprobes arc_kprobe_handler(unsigned long addr, struct
> pt_regs *regs)
> | ^~~~~~~~~~~~~~~~~~
> In file included from arch/arc/include/asm/mmu.h:21,
> from arch/arc/include/asm/pgtable.h:14,
> from include/linux/pgtable.h:6,
> from include/asm-generic/io.h:1047,
> from arch/arc/include/asm/io.h:232,
> from include/linux/io.h:13,
> from kernel/dma/coherent.c:6:
> arch/arc/include/asm/mmu-arcv2.h: In function 'mmu_setup_asid':
> arch/arc/include/asm/mmu-arcv2.h:82:2: error: implicit declaration of
> function 'write_aux_reg' [-Werror=implicit-function-declaration]
> 82 | write_aux_reg(ARC_REG_PID, asid | MMU_ENABLE);
> | ^~~~~~~~~~~~~
> cc1: some warnings being treated as errors
Thx for the report. Fix posted for first 2 warnings [1]
I can't reproduce the last warning about write_aux_reg() despite using
the config from 3rd link below.
-Vineet
[1]
http://lists.infradead.org/pipermail/linux-snps-arc/2024-March/007916.html
>
> Steps to reproduce:
> -------
> # tuxmake --runtime podman --target-arch arc --toolchain gcc-9
> --kconfig defconfig
>
>
> Links:
> - https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20240325/testrun/23149630/suite/build/test/gcc-9-defconfig/log
> - https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20240325/testrun/23149630/suite/build/test/gcc-9-defconfig/history/
> - https://storage.tuxsuite.com/public/linaro/lkft/builds/2eA2VSZdDsL0DMBBhjoauN9IVoK/
>
> --
> Linaro LKFT
> https://lkft.linaro.org
prev parent reply other threads:[~2024-03-28 5:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 6:39 next: arc: defconfig - gcc-9 - mmu-arcv2.h:82:2: error: implicit declaration of function 'write_aux_reg' [-Werror=implicit-function-declaration] Naresh Kamboju
2024-03-28 5:46 ` Vineet Gupta [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=d22054a8-76d3-4ae2-9e20-38a7a8ce902d@kernel.org \
--to=vgupta@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=regressions@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).