From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: linux-parisc@vger.kernel.org,
open list <linux-kernel@vger.kernel.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Helge Deller <deller@gmx.de>,
"James E.J. Bottomley" <James.Bottomley@hansenpartnership.com>
Subject: parisc: stacktrace.c:25:21: error: implicit declaration of function '__kernel_text_address'
Date: Fri, 5 Nov 2021 17:30:06 +0530 [thread overview]
Message-ID: <CA+G9fYvPOHh_O4qtU=GKktTxR_G8tjFXjTsecSp2gTkHKeujSA@mail.gmail.com> (raw)
[Please ignore this email if it is already reported ]
Regression found on parisc gcc-8/9/10 and gcc-11 built with defconfig
Following build warnings / errors reported on linux next 20211105.
metadata:
git_describe: next-20211105
git_repo: https://gitlab.com/Linaro/lkft/mirrors/next/linux-next
git_short_log: b477ae38e815 (\"Add linux-next specific files for 20211105\")
target_arch: parisc
toolchain: gcc-11
build error :
--------------
<stdin>:1559:2: warning: #warning syscall futex_waitv not implemented [-Wcpp]
arch/parisc/kernel/stacktrace.c: In function 'walk_stackframe':
arch/parisc/kernel/stacktrace.c:25:21: error: implicit declaration of
function '__kernel_text_address'
[-Werror=implicit-function-declaration]
25 | if (__kernel_text_address(info.ip))
| ^~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
make[3]: *** [scripts/Makefile.build:288:
arch/parisc/kernel/stacktrace.o] Error 1
Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
build link:
-----------
https://builds.tuxbuild.com/20U3L7IKgdLoEJQrfGdwlmczMDy/build.log
build config:
-------------
https://builds.tuxbuild.com/20U3L7IKgdLoEJQrfGdwlmczMDy/config
# To install tuxmake on your system globally
# sudo pip3 install -U tuxmake
tuxmake --runtime podman --target-arch parisc --toolchain gcc-11
--kconfig defconfig
--
Linaro LKFT
https://lkft.linaro.org
reply other threads:[~2021-11-05 12:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CA+G9fYvPOHh_O4qtU=GKktTxR_G8tjFXjTsecSp2gTkHKeujSA@mail.gmail.com' \
--to=naresh.kamboju@linaro.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=deller@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).