From: kbuild test robot <lkp@intel.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: kbuild-all@01.org, syzkaller@googlegroups.com,
vegard.nossum@oracle.com, catalin.marinas@arm.com,
taviso@google.com, will.deacon@arm.com,
linux-kernel@vger.kernel.org, quentin.casasnovas@oracle.com,
kcc@google.com, edumazet@google.com, glider@google.com,
keescook@google.com, bhelgaas@google.com, sasha.levin@oracle.com,
akpm@linux-foundation.org, drysdale@google.com,
linux-arm-kernel@lists.infradead.org, ard.biesheuvel@linaro.org,
ryabinin.a.a@gmail.com, kirill@shutemov.name,
Dmitry Vyukov <dvyukov@google.com>
Subject: Re: [PATCH v6] kernel: add kcov code coverage
Date: Mon, 25 Jan 2016 21:53:49 +0800 [thread overview]
Message-ID: <201601252108.oXiP6kOR%fengguang.wu@intel.com> (raw)
In-Reply-To: <1453726850-49137-1-git-send-email-dvyukov@google.com>
[-- Attachment #1: Type: text/plain, Size: 1738 bytes --]
Hi Dmitry,
[auto build test ERROR on v4.5-rc1]
[also build test ERROR on next-20160125]
[cannot apply to tip/x86/core kbuild/for-next]
[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/20160125-210230
config: x86_64-allyesconfig (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
>> Makefile:679: 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]: *** [arch/x86/purgatory/purgatory.o] Error 1
>> gcc-5: error: unrecognized command line option '-fsanitize-coverage=trace-pc'
make[2]: *** [arch/x86/purgatory/sha256.o] Error 1
>> gcc-5: error: unrecognized command line option '-fsanitize-coverage=trace-pc'
make[2]: *** [arch/x86/purgatory/string.o] Error 1
make[2]: Target 'arch/x86/purgatory/kexec-purgatory.c' not remade because of errors.
make[1]: *** [archprepare] Error 2
make[1]: Target 'prepare' not remade because of errors.
make: *** [sub-make] Error 2
vim +679 Makefile
673 endif
674 endif
675 KBUILD_CFLAGS += $(stackp-flag)
676
677 ifdef CONFIG_KCOV
678 ifeq ($(call cc-option, $(CFLAGS_KCOV)),)
> 679 $(warning Cannot use CONFIG_KCOV: \
680 -fsanitize-coverage=trace-pc is not supported by compiler)
681 endif
682 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: 52342 bytes --]
next prev parent reply other threads:[~2016-01-25 13:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 13:00 Dmitry Vyukov
2016-01-25 13:03 ` Dmitry Vyukov
2016-01-25 15:38 ` Kirill A. Shutemov
2016-01-25 13:53 ` kbuild test robot [this message]
2016-01-28 12:30 ` Alexander Shishkin
2016-02-02 16:02 ` Andrey Ryabinin
2016-02-04 15:07 ` Dmitry Vyukov
2016-02-04 15:19 ` Andrey Ryabinin
2016-02-02 17:19 ` Jiri Slaby
2016-02-04 15:07 ` Dmitry Vyukov
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=201601252108.oXiP6kOR%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=ard.biesheuvel@linaro.org \
--cc=bhelgaas@google.com \
--cc=catalin.marinas@arm.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=kirill@shutemov.name \
--cc=linux-arm-kernel@lists.infradead.org \
--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 \
--cc=will.deacon@arm.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®