From: kbuild test robot <lkp@intel.com>
To: Greg Hackmann <ghackmann@android.com>
Cc: kbuild-all@01.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>
Subject: [linux-next:master 4291/4370] kernel/gcov/gcc_4_7.c:162:9: error: implicit declaration of function 'within_module'
Date: Fri, 29 Mar 2019 14:50:59 +0800 [thread overview]
Message-ID: <201903291457.5NspQgJn%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1453 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 1baf02ec984b88b435e2fa065300179a3f48e7d2
commit: 8c3d220cb6b5f502745285106154bad632f43b15 [4291/4370] gcov: clang support
config: x86_64-randconfig-u0-03291354 (attached as .config)
compiler: gcc-5 (Debian 5.5.0-3) 5.4.1 20171010
reproduce:
git checkout 8c3d220cb6b5f502745285106154bad632f43b15
# save the attached .config to linux build tree
make ARCH=x86_64
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:9: error: implicit declaration of function 'within_module' [-Werror=implicit-function-declaration]
return within_module((unsigned long)info, mod);
^
cc1: some warnings being treated as errors
vim +/within_module +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 kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 31814 bytes --]
reply other threads:[~2019-03-29 6:51 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=201903291457.5NspQgJn%lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=ghackmann@android.com \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=ndesaulniers@google.com \
--cc=oberpar@linux.ibm.com \
--cc=trong@android.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).