linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <fengguang.wu@intel.com>
To: Andrey Ryabinin <a.ryabinin@samsung.com>
Cc: kbuild-all@01.org, Ben Hutchings <bwh@kernel.org>,
	Andrey Konovalov <adech.fo@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Memory Management List <linux-mm@kvack.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Arnd Bergmann <arnd@arndb.de>
Subject: [linux-stable-rc:linux-3.16.y 2872/3092] head32.c:undefined reference to `__gcov_exit'
Date: Tue, 28 Nov 2017 09:54:58 +0800	[thread overview]
Message-ID: <201711280954.IZTTcdSy%fengguang.wu@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1607 bytes --]

Hi Andrey,

It's probably a bug fix that unveils the link errors.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-3.16.y
head:   c45c05f42d5d3baf5d18e648c064788381fcfa1c
commit: 3cb0dc19883f0c69225311d4f76aa8128d3681a4 [2872/3092] module: fix types of device tables aliases
config: i386-allmodconfig (attached as .config)
compiler: gcc-7 (Debian 7.2.0-12) 7.2.1 20171025
reproduce:
        git checkout 3cb0dc19883f0c69225311d4f76aa8128d3681a4
        # save the attached .config to linux build tree
        make ARCH=i386 

All errors (new ones prefixed by >>):

   arch/x86/kernel/head32.o: In function `_GLOBAL__sub_D_00100_1_i386_start_kernel':
>> head32.c:(.text.exit+0x4): undefined reference to `__gcov_exit'
   arch/x86/kernel/head.o: In function `_GLOBAL__sub_D_00100_1_reserve_ebda_region':
   head.c:(.text.exit+0x4): undefined reference to `__gcov_exit'
   init/built-in.o: In function `_GLOBAL__sub_D_00100_1___ksymtab_system_state':
   main.c:(.text.exit+0x4): undefined reference to `__gcov_exit'
   init/built-in.o: In function `_GLOBAL__sub_D_00100_1_root_mountflags':
   do_mounts.c:(.text.exit+0xe): undefined reference to `__gcov_exit'
   init/built-in.o: In function `_GLOBAL__sub_D_00100_1_initrd_load':
   do_mounts_initrd.c:(.text.exit+0x18): undefined reference to `__gcov_exit'
   init/built-in.o:initramfs.c:(.text.exit+0x22): more undefined references to `__gcov_exit' follow

---
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: 46363 bytes --]

                 reply	other threads:[~2017-11-28  1:55 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=201711280954.IZTTcdSy%fengguang.wu@intel.com \
    --to=fengguang.wu@intel.com \
    --cc=a.ryabinin@samsung.com \
    --cc=adech.fo@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=bwh@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kbuild-all@01.org \
    --cc=linux-mm@kvack.org \
    /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).