From: Philip Li <philip.li@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [linux-stable-rc:linux-5.4.y 2066/5257] ubsan.c:undefined reference to `__ashlti3'
Date: Thu, 21 May 2020 09:22:15 +0800 [thread overview]
Message-ID: <20200521012215.GB12021@intel.com> (raw)
In-Reply-To: <aa2b91e9-17bc-3819-fea4-7ac1c64d011f@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 2086 bytes --]
On Wed, May 20, 2020 at 08:34:23PM +0800, Kefeng Wang wrote:
>
> On 2020/5/20 14:54, kbuild test robot wrote:
> > 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'
>
> My patch is irrelevant，it seems that the following patch fix build error.
thanks for the input, we will check this false positive. Sorry for
the noise.
>
> commit fc585d4a5cf614727f64d86550b794bcad29d5c3
> Author: Olof Johansson <olof@lixom.net>
> Date: Mon Dec 16 20:06:31 2019 -0800
>
> riscv: Less inefficient gcc tishift helpers (and export their symbols)
>
>
> > ---
> > 0-DAY CI Kernel Test Service, Intel Corporation
> > https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
> _______________________________________________
> kbuild-all mailing list -- kbuild-all(a)lists.01.org
> To unsubscribe send an email to kbuild-all-leave(a)lists.01.org
next prev parent reply other threads:[~2020-05-21 1:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 6:54 [linux-stable-rc:linux-5.4.y 2066/5257] ubsan.c:undefined reference to `__ashlti3' kbuild test robot
2020-05-20 12:34 ` Kefeng Wang
2020-05-21 1:22 ` Philip Li [this message]
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=20200521012215.GB12021@intel.com \
--to=philip.li@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.