From: Pedro Falcato <pedro.falcato@gmail.com>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: kernel test robot <lkp@intel.com>,
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] lib/bch.c:317:undefined reference to `__paritydi2'
Date: Fri, 31 Jan 2025 14:34:32 +0000 [thread overview]
Message-ID: <CAKbZUD0N7bkuw_Le3Pr9o1V2BjjcY_YiLm8a8DPceubTdZ00GQ@mail.gmail.com> (raw)
In-Reply-To: <CAFULd4bYhA+XsJH3rr=i98O4DJr_jjZe5HtBETGV_4Sm0S0QnQ@mail.gmail.com>
On Fri, Jan 31, 2025 at 1:23 PM Uros Bizjak <ubizjak@gmail.com> wrote:
>
> On Fri, Jan 31, 2025 at 2:12 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: arm64-randconfig-002-20250131 (https://download.01.org/0day-ci/archive/20250131/202501312159.l6jNRaYy-lkp@intel.com/config)
> > compiler: aarch64-linux-gcc (GCC) 14.2.0
> > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250131/202501312159.l6jNRaYy-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/202501312159.l6jNRaYy-lkp@intel.com/
> >
> > All errors (new ones prefixed by >>):
> >
> > aarch64-linux-ld: lib/bch.o: in function `parity':
> > >> lib/bch.c:317:(.text+0x10e8): undefined reference to `__paritydi2'
> > >> lib/bch.c:317:(.text+0x10e8): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `__paritydi2'
>
> This config for some reason generates a call to the library function.
> But I have tested this with a crosscompiler:
>
> fmov s31, w0
> cnt v31.8b, v31.8b
> addv b31, v31.8b
> fmov w0, s31
> and w0, w0, 1
> ret
>
> It looks that __has_builtin() does not mean that there will be no call
> to a library function?!
Yep, __builtin functions aren't strictly required to be inlined and
can generate a library call if the compiler so chooses (how often this
happens depends on the optimization level and architecture).
e.g: https://godbolt.org/z/zKPb9hbaM
--
Pedro
next prev parent reply other threads:[~2025-01-31 14:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-31 13:12 kernel test robot
2025-01-31 13:19 ` Uros Bizjak
2025-01-31 14:34 ` Pedro Falcato [this message]
2025-01-31 15:42 ` Uros Bizjak
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=CAKbZUD0N7bkuw_Le3Pr9o1V2BjjcY_YiLm8a8DPceubTdZ00GQ@mail.gmail.com \
--to=pedro.falcato@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ubizjak@gmail.com \
/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