From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: open list <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
lkft-triage@lists.linaro.org,
Linux Regressions <regressions@lists.linux.dev>,
rcu <rcu@vger.kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Dan Carpenter <dan.carpenter@linaro.org>,
"Paul E. McKenney" <paulmck@kernel.org>,
Joel Fernandes <joel@joelfernandes.org>,
eeraj.upadhyay@kernel.org,
John Ogness <john.ogness@linutronix.de>
Subject: Re: arm-linux-gnueabihf-ld: kernel/rcu/update.o:update.c:(.text+0x1cc4): more undefined references to `__bad_cmpxchg' follow
Date: Thu, 30 May 2024 13:26:35 +0100 [thread overview]
Message-ID: <Zlhwe5owmbzI3jJK@shell.armlinux.org.uk> (raw)
In-Reply-To: <CA+G9fYuZ+pf6p8AXMZWtdFtX-gbG8HMaBKp=XbxcdzA_QeLkxQ@mail.gmail.com>
On Thu, May 30, 2024 at 05:50:52PM +0530, Naresh Kamboju wrote:
> The arm builds failed on Linux next with gcc-13 and clang-18.
>
> Config: arm imx_v6_v7_defconfig - failed
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> Build log:
> -----
> arm-linux-gnueabihf-ld: kernel/rcu/update.o: in function
> `rcu_trc_cmpxchg_need_qs':
> update.c:(.text+0x348): undefined reference to `__bad_cmpxchg'
> arm-linux-gnueabihf-ld: kernel/rcu/update.o: in function
> `rcu_read_unlock_trace_special':
> update.c:(.text+0x41c): undefined reference to `__bad_cmpxchg'
> arm-linux-gnueabihf-ld: kernel/rcu/update.o: in function
> `trc_read_check_handler':
> update.c:(.text+0x4b0): undefined reference to `__bad_cmpxchg'
> arm-linux-gnueabihf-ld: kernel/rcu/update.o: in function `trc_inspect_reader':
> update.c:(.text+0x1518): undefined reference to `__bad_cmpxchg'
> arm-linux-gnueabihf-ld: update.c:(.text+0x1548): undefined reference
> to `__bad_cmpxchg'
> arm-linux-gnueabihf-ld: kernel/rcu/update.o:update.c:(.text+0x1cc4):
> more undefined references to `__bad_cmpxchg' follow
> make[3]: *** [/builds/linux/scripts/Makefile.vmlinux:34: vmlinux] Error 1
You get a reference to __bad_cmpxchg() when someone uses cmpxchg() on
a datatype that there are no CPU instructions to perform the atomic
compare-and-exchange.
As we support 8-bit, 16-bit and 32-bit, I would expect that we're now
seeing cmpxchg() being used on 64-bit values, which are unsupportable
on 32-bit Arm.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
WARNING: multiple messages have this Message-ID (diff)
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: open list <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
lkft-triage@lists.linaro.org,
Linux Regressions <regressions@lists.linux.dev>,
rcu <rcu@vger.kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Dan Carpenter <dan.carpenter@linaro.org>,
"Paul E. McKenney" <paulmck@kernel.org>,
Joel Fernandes <joel@joelfernandes.org>,
eeraj.upadhyay@kernel.org,
John Ogness <john.ogness@linutronix.de>
Subject: Re: arm-linux-gnueabihf-ld: kernel/rcu/update.o:update.c:(.text+0x1cc4): more undefined references to `__bad_cmpxchg' follow
Date: Thu, 30 May 2024 13:26:35 +0100 [thread overview]
Message-ID: <Zlhwe5owmbzI3jJK@shell.armlinux.org.uk> (raw)
In-Reply-To: <CA+G9fYuZ+pf6p8AXMZWtdFtX-gbG8HMaBKp=XbxcdzA_QeLkxQ@mail.gmail.com>
On Thu, May 30, 2024 at 05:50:52PM +0530, Naresh Kamboju wrote:
> The arm builds failed on Linux next with gcc-13 and clang-18.
>
> Config: arm imx_v6_v7_defconfig - failed
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> Build log:
> -----
> arm-linux-gnueabihf-ld: kernel/rcu/update.o: in function
> `rcu_trc_cmpxchg_need_qs':
> update.c:(.text+0x348): undefined reference to `__bad_cmpxchg'
> arm-linux-gnueabihf-ld: kernel/rcu/update.o: in function
> `rcu_read_unlock_trace_special':
> update.c:(.text+0x41c): undefined reference to `__bad_cmpxchg'
> arm-linux-gnueabihf-ld: kernel/rcu/update.o: in function
> `trc_read_check_handler':
> update.c:(.text+0x4b0): undefined reference to `__bad_cmpxchg'
> arm-linux-gnueabihf-ld: kernel/rcu/update.o: in function `trc_inspect_reader':
> update.c:(.text+0x1518): undefined reference to `__bad_cmpxchg'
> arm-linux-gnueabihf-ld: update.c:(.text+0x1548): undefined reference
> to `__bad_cmpxchg'
> arm-linux-gnueabihf-ld: kernel/rcu/update.o:update.c:(.text+0x1cc4):
> more undefined references to `__bad_cmpxchg' follow
> make[3]: *** [/builds/linux/scripts/Makefile.vmlinux:34: vmlinux] Error 1
You get a reference to __bad_cmpxchg() when someone uses cmpxchg() on
a datatype that there are no CPU instructions to perform the atomic
compare-and-exchange.
As we support 8-bit, 16-bit and 32-bit, I would expect that we're now
seeing cmpxchg() being used on 64-bit values, which are unsupportable
on 32-bit Arm.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-05-30 12:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 12:20 arm-linux-gnueabihf-ld: kernel/rcu/update.o:update.c:(.text+0x1cc4): more undefined references to `__bad_cmpxchg' follow Naresh Kamboju
2024-05-30 12:20 ` Naresh Kamboju
2024-05-30 12:26 ` Russell King (Oracle) [this message]
2024-05-30 12:26 ` Russell King (Oracle)
2024-05-30 13:27 ` Arnd Bergmann
2024-05-30 13:27 ` Arnd Bergmann
2024-05-30 16:37 ` Paul E. McKenney
2024-05-30 16:37 ` Paul E. McKenney
2024-05-30 17:24 ` Paul E. McKenney
2024-05-30 17:24 ` Paul E. McKenney
2024-05-30 18:05 ` Arnd Bergmann
2024-05-30 18:05 ` Arnd Bergmann
2024-05-30 18:21 ` Paul E. McKenney
2024-05-30 18:21 ` Paul E. McKenney
2024-05-30 21:52 ` Nathan Chancellor
2024-05-30 21:52 ` Nathan Chancellor
2024-05-30 22:05 ` Paul E. McKenney
2024-05-30 22:05 ` Paul E. McKenney
2024-05-30 23:30 ` Nathan Chancellor
2024-05-30 23:30 ` Nathan Chancellor
2024-05-31 0:35 ` Paul E. McKenney
2024-05-31 0:35 ` Paul E. McKenney
2024-05-31 16:27 ` Nathan Chancellor
2024-05-31 16:27 ` Nathan Chancellor
2024-05-31 19:42 ` Paul E. McKenney
2024-05-31 19:42 ` Paul E. McKenney
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=Zlhwe5owmbzI3jJK@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=arnd@arndb.de \
--cc=dan.carpenter@linaro.org \
--cc=eeraj.upadhyay@kernel.org \
--cc=joel@joelfernandes.org \
--cc=john.ogness@linutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=regressions@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 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.