Received-SPF: pass (google.com: domain of linux-kernel+bounces-20298-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1;
Precedence: bulk
MIME-Version: 1.0
References: <CAJNi4rO+Dw5qYDtyJVbuo0OqAoXpGq_Qq6xjH9cvMCAUnW+77g@mail.gmail.com>
 <CAJNi4rMHtM=39jzkzwqt++kVpSp0=XfDrVdY94WoW6B34oKwDA@mail.gmail.com>
 <ZZb2f0U4qTWDjCGj@FVFF77S0Q05N.cambridge.arm.com> <CAJNi4rOpzmQAW1Fjst-Em=SQ7q8QsQh0PWhVxUizrOW9JukOgQ@mail.gmail.com>
 <ZZvS8rigFJR8L56c@FVFF77S0Q05N>
In-Reply-To: <ZZvS8rigFJR8L56c@FVFF77S0Q05N>
From: richard clark <richard.xnu.clark@gmail.com>
Date: Tue, 9 Jan 2024 10:52:23 +0800
Message-ID: <CAJNi4rNTzkuZeya8f=tBVOn_dqgLbLf1A+3X4vHqiSa_sgDbUA@mail.gmail.com>
Subject: Re: undefined reference to `__aarch64_cas4_sync' error on arm64
 native build
To: Mark Rutland <mark.rutland@arm.com>
Cc: gcc-help@gcc.gnu.org, linux-kernel@vger.kernel.org, 
	linux-arm-kernel@lists.infradead.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, Jan 8, 2024 at 6:51=E2=80=AFPM Mark Rutland <mark.rutland@arm.com> =
wrote:

>
> This is due to a difference in default options between the two compilers;=
 the
> kernel isn't linked against libc in either case.
>
> Your native compiler evidently has -moutline-atomics enabled in its defau=
lt
> options. With that enabled, the builtin atomics generate calls to out-of-=
line
> functions which the kernel itself does not provide, and hence those resul=
t in a
> link-time error.
>
> Your cross-compiler evidently does not have -moutline-atomics enabled in =
its
> default options. Without that enabled, the builtin atomics generate inlin=
e
> atomic instructions rather than function calls. Since these don't depend =
on
> external functions there's no link-time error.
>
> If you pass 'mno-outline-atomics' to your native compiler, the problem sh=
ould
> disappear.
>
Right, this should be the root cause, just pass 'mno-outline-atomics'
to my native compiler, the kernel link time issue doesn't show. But, I
test a userland application with '__sync_val_compare_and_swap' used,
for the 'aarch64-linux-gnu-gcc test.c', the 'nm a.out' will output:
..
0000000000000960 t __aarch64_cas4_sync
0000000000011011 B __aarch64_have_lse_atomics
..
From the above output, seems the cross compiler has
'-moutline-atomics' enabled by default, also with
'aarch64-linux-gnu-gcc -mno-outline-atomics test.c', the 'nm a.out'
doesn't show the '_aarch64_cas4_sync'. The same result for the native
build for the same test.c, this result can't explain why the
cross-compile linux kernel will not generate the link time error,...

>
> Mark.