From: kbuild test robot <lkp@intel.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: kbuild-all@01.org, akpm@linux-foundation.org,
drysdale@google.com, keescook@google.com,
quentin.casasnovas@oracle.com, sasha.levin@oracle.com,
vegard.nossum@oracle.com, linux-kernel@vger.kernel.org,
edumazet@google.com, taviso@google.com, bhelgaas@google.com,
syzkaller@googlegroups.com, kcc@google.com, glider@google.com,
ryabinin.a.a@gmail.com, Dmitry Vyukov <dvyukov@google.com>
Subject: Re: [PATCH v2] kernel: add kcov code coverage
Date: Thu, 14 Jan 2016 06:31:23 +0800 [thread overview]
Message-ID: <201601140644.Gmkq6w80%fengguang.wu@intel.com> (raw)
In-Reply-To: <1452689318-107172-1-git-send-email-dvyukov@google.com>
[-- Attachment #1: Type: text/plain, Size: 1510 bytes --]
Hi Dmitry,
[auto build test ERROR on kbuild/for-next]
[also build test ERROR on v4.4]
[cannot apply to tip/x86/core next-20160113]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
url: https://github.com/0day-ci/linux/commits/Dmitry-Vyukov/kernel-add-kcov-code-coverage/20160113-205004
base: https://git.kernel.org/pub/scm/linux/kernel/git/mmarek/kbuild.git for-next
config: x86_64-randconfig-n0-01140517 (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
>> Makefile:695: Cannot use CONFIG_KCOV: -fsanitize-coverage=trace-pc is not supported by compiler
gcc-5: error: unrecognized command line option '-fsanitize-coverage=trace-pc'
make[2]: *** [kernel/bounds.s] Error 1
make[2]: Target '__build' not remade because of errors.
make[1]: *** [prepare0] Error 2
make[1]: Target 'prepare' not remade because of errors.
make: *** [sub-make] Error 2
vim +695 Makefile
689 endif
690 endif
691 KBUILD_CFLAGS += $(stackp-flag)
692
693 ifdef CONFIG_KCOV
694 ifeq ($(call cc-option, $(CFLAGS_KCOV)),)
> 695 $(warning Cannot use CONFIG_KCOV: \
696 -fsanitize-coverage=trace-pc is not supported by compiler)
697 endif
698 endif
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 25569 bytes --]
next prev parent reply other threads:[~2016-01-13 22:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 12:48 Dmitry Vyukov
2016-01-13 22:31 ` kbuild test robot [this message]
2016-01-14 9:03 ` Kirill A. Shutemov
2016-01-14 9:10 ` Dmitry Vyukov
2016-01-14 9:23 ` Kirill A. Shutemov
2016-01-14 12:21 ` Dmitry Vyukov
2016-01-14 12:35 ` Kirill A. Shutemov
2016-01-14 12:49 ` Kirill A. Shutemov
2016-01-14 14:24 ` Dmitry Vyukov
2016-01-14 10:50 ` Andrey Ryabinin
2016-01-14 14:30 ` Dmitry Vyukov
2016-01-15 13:05 ` Andrey Ryabinin
2016-01-15 13:42 ` Will Deacon
2016-01-15 14:07 ` Dmitry Vyukov
2016-01-18 13:34 ` Andrey Ryabinin
2016-01-18 19:31 ` Dmitry Vyukov
2016-01-18 14:13 ` Mark Rutland
2016-01-18 19:44 ` Dmitry Vyukov
2016-01-18 20:09 ` Dmitry Vyukov
2016-01-22 11:55 ` Mark Rutland
2016-01-22 12:15 ` Dmitry Vyukov
2016-01-22 12:52 ` Mark Rutland
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=201601140644.Gmkq6w80%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=bhelgaas@google.com \
--cc=drysdale@google.com \
--cc=dvyukov@google.com \
--cc=edumazet@google.com \
--cc=glider@google.com \
--cc=kbuild-all@01.org \
--cc=kcc@google.com \
--cc=keescook@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=quentin.casasnovas@oracle.com \
--cc=ryabinin.a.a@gmail.com \
--cc=sasha.levin@oracle.com \
--cc=syzkaller@googlegroups.com \
--cc=taviso@google.com \
--cc=vegard.nossum@oracle.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
all inboxes | Powered by JetHome®