From: Uros Bizjak <ubizjak@gmail.com>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [akpm-mm:mm-nonmm-unstable 52/52] bch.c:undefined reference to `__paritydi2'
Date: Fri, 31 Jan 2025 14:25:54 +0100 [thread overview]
Message-ID: <CAFULd4Y7r-ELNr-XBP2u6Ka1JCgYGYn_yOu25h9ehBNbzuG3TQ@mail.gmail.com> (raw)
In-Reply-To: <202501312051.0vJPrrIL-lkp@intel.com>
On Fri, Jan 31, 2025 at 2:02 PM kernel test robot <lkp@intel.com> wrote:
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-nonmm-unstable
> head: 1b9f78ccbffefb107cd92e20cfccd03ff2fa9d0e
> commit: 1b9f78ccbffefb107cd92e20cfccd03ff2fa9d0e [52/52] lib/bch.c: use __builtin_parity() when available
> config: loongarch-randconfig-001-20250131 (https://download.01.org/0day-ci/archive/20250131/202501312051.0vJPrrIL-lkp@intel.com/config)
> compiler: loongarch64-linux-gcc (GCC) 14.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250131/202501312051.0vJPrrIL-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202501312051.0vJPrrIL-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> loongarch64-linux-ld: lib/bch.o: in function `solve_linear_system.constprop.0.isra.0':
> >> bch.c:(.text+0xd18): undefined reference to `__paritydi2'
Hm, my config cross-compiles to:
bstrpick.d $r4,$r4,31,0
vrepli.d $vr0,0
vinsgr2vr.d $vr0,$r4,0
vpcnt.d $vr0,$vr0
vpickve2gr.du $r4,$vr0,0
andi $r4,$r4,1
jr $r1
It looks that __has_builtin() does not mean that there will be no call
to a library function?!
Uros.
prev parent reply other threads:[~2025-01-31 13:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-31 13:01 kernel test robot
2025-01-31 13:25 ` Uros Bizjak [this message]
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=CAFULd4Y7r-ELNr-XBP2u6Ka1JCgYGYn_yOu25h9ehBNbzuG3TQ@mail.gmail.com \
--to=ubizjak@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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