linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: kbuild-all@01.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Memory Management List <linux-mm@kvack.org>,
	Sasha Levin <alexander.levin@microsoft.com>
Subject: [linux-stable-rc:linux-4.9.y 9986/9999] ptrace.c:undefined reference to `abort'
Date: Sat, 6 Jul 2019 00:08:59 +0800	[thread overview]
Message-ID: <201907060045.bQY0GTP0%lkp@intel.com> (raw)

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

tree:   https://kernel.googlesource.com/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.9.y
head:   af13e6db0db43996e060d2b9ca57f60b09d08cb8
commit: 273b0e9d8a3e0970fab8ad1b037adf9e3a9fc63b [9986/9999] bug.h: work around GCC PR82365 in BUG()
config: arc-defconfig (attached as .config)
compiler: arc-elf-gcc (GCC) 7.4.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        git checkout 273b0e9d8a3e0970fab8ad1b037adf9e3a9fc63b
        # save the attached .config to linux build tree
        GCC_VERSION=7.4.0 make.cross ARCH=arc 

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   arch/arc/built-in.o: In function `genregs_set':
>> ptrace.c:(.text+0x9bc): undefined reference to `abort'
>> ptrace.c:(.text+0x9bc): undefined reference to `abort'
   arch/arc/built-in.o: In function `genregs_get':
   ptrace.c:(.text+0x2de8): undefined reference to `abort'
   ptrace.c:(.text+0x2de8): undefined reference to `abort'
   arch/arc/built-in.o: In function `arc_pmu_device_probe':
>> perf_event.c:(.text+0x99e6): undefined reference to `abort'
   arch/arc/built-in.o:perf_event.c:(.text+0x99e6): more undefined references to `abort' 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: 7715 bytes --]

             reply	other threads:[~2019-07-05 16:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-05 16:08 kbuild test robot [this message]
2019-07-05 16:15 ` Greg Kroah-Hartman
2019-07-05 16:31   ` Arnd Bergmann
2019-07-05 18:24     ` Greg Kroah-Hartman

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=201907060045.bQY0GTP0%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=alexander.levin@microsoft.com \
    --cc=arnd@arndb.de \
    --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