All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [linux-stable-rc:linux-5.4.y 2066/5257] ubsan.c:undefined reference to `__ashlti3'
Date: Wed, 20 May 2020 14:54:58 +0800	[thread overview]
Message-ID: <20200520065458.GC12637@intel.com> (raw)

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

Hi Kefeng,

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-5.4.y
head:   cac6eb2794c85e7777fb0caac6fa75b6364d81a0
commit: 1865d6440fb63ad979d7034b2d7c94937bfd2200 [2066/5257] PCI: mobiveil: Fix csr_read()/write() build issue
config: riscv-allyesconfig (attached as .config)
compiler: riscv64-linux-gcc (GCC) 9.3.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 1865d6440fb63ad979d7034b2d7c94937bfd2200
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=riscv 

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

All errors (new ones prefixed by >>, old ones prefixed by <<):

riscv64-linux-ld: lib/ubsan.o: in function `.L2':
>> ubsan.c:(.text.unlikely+0x38): undefined reference to `__ashlti3'
>> riscv64-linux-ld: ubsan.c:(.text.unlikely+0x42): undefined reference to `__ashrti3'

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 60416 bytes --]

             reply	other threads:[~2020-05-20  6:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-20  6:54 kbuild test robot [this message]
2020-05-20 12:34 ` [linux-stable-rc:linux-5.4.y 2066/5257] ubsan.c:undefined reference to `__ashlti3' Kefeng Wang
2020-05-21  1:22   ` Philip Li
2020-05-26  9:53   ` 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=20200520065458.GC12637@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.