From: kernel test robot <lkp@intel.com>
To: Greg Hackmann <ghackmann@android.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Nick Desaulniers <ndesaulniers@google.com>,
Tri Vo <trong@android.com>,
Peter Oberparleiter <oberpar@linux.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Yu Zhao <yuzhao@google.com>, Sean Paul <seanpaul@chromium.org>
Subject: [jsarha:topic/chromeos-4.19-s0ix 9206/9999] kernel/gcov/gcc_4_7.c:162:16: error: implicit declaration of function 'within_module'; did you mean 'init_module'?
Date: Tue, 12 Apr 2022 01:52:45 +0800 [thread overview]
Message-ID: <202204120122.ULP2Vs6G-lkp@intel.com> (raw)
Hi Greg,
FYI, the error/warning still remains.
tree: https://github.com/jsarha/linux topic/chromeos-4.19-s0ix
head: 430bdaa0a8c38697780f45a148964d71951df11f
commit: 35be48648a6552869bd5d6c9a0d278102d23d46c [9206/9999] UPSTREAM: gcov: clang support
config: openrisc-randconfig-s032-20220411 (https://download.01.org/0day-ci/archive/20220412/202204120122.ULP2Vs6G-lkp@intel.com/config)
compiler: or1k-linux-gcc (GCC) 11.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# apt-get install sparse
# sparse version: v0.6.4-dirty
# https://github.com/jsarha/linux/commit/35be48648a6552869bd5d6c9a0d278102d23d46c
git remote add jsarha https://github.com/jsarha/linux
git fetch --no-tags jsarha topic/chromeos-4.19-s0ix
git checkout 35be48648a6552869bd5d6c9a0d278102d23d46c
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=openrisc SHELL=/bin/bash M=kernel/gcov
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
kernel/gcov/gcc_4_7.c: In function 'gcov_info_within_module':
>> kernel/gcov/gcc_4_7.c:162:16: error: implicit declaration of function 'within_module'; did you mean 'init_module'? [-Werror=implicit-function-declaration]
162 | return within_module((unsigned long)info, mod);
| ^~~~~~~~~~~~~
| init_module
cc1: some warnings being treated as errors
vim +162 kernel/gcov/gcc_4_7.c
152
153 /**
154 * gcov_info_within_module - check if a profiling data set belongs to a module
155 * @info: profiling data set
156 * @mod: module
157 *
158 * Returns true if profiling data belongs module, false otherwise.
159 */
160 bool gcov_info_within_module(struct gcov_info *info, struct module *mod)
161 {
> 162 return within_module((unsigned long)info, mod);
163 }
164
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next reply other threads:[~2022-04-11 17:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 17:52 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-05-02 19:25 [jsarha:topic/chromeos-4.19-s0ix 9206/9999] kernel/gcov/gcc_4_7.c:162:16: error: implicit declaration of function 'within_module'; did you mean 'init_module'? kernel test robot
2022-10-30 22:45 kernel test robot
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=202204120122.ULP2Vs6G-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=ghackmann@android.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ndesaulniers@google.com \
--cc=oberpar@linux.ibm.com \
--cc=seanpaul@chromium.org \
--cc=trong@android.com \
--cc=yuzhao@google.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;
as well as URLs for NNTP newsgroup(s).