From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from foss.arm.com (foss.arm.com [217.140.110.172])
	by smtp.subspace.kernel.org (Postfix) with ESMTP id 3B72514F94
	for <linux-kernel@vger.kernel.org>; Thu, 11 Jan 2024 11:26:36 +0000 (UTC)
Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=arm.com
Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=arm.com
Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14])
	by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 467342F4;
	Thu, 11 Jan 2024 03:27:22 -0800 (PST)
Received: from FVFF77S0Q05N (unknown [10.57.90.43])
	by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 667C03F64C;
	Thu, 11 Jan 2024 03:26:35 -0800 (PST)
Date: Thu, 11 Jan 2024 11:26:32 +0000
From: Mark Rutland <mark.rutland@arm.com>
To: richard clark <richard.xnu.clark@gmail.com>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
	Xi Ruoyao <xry111@xry111.site>, gcc-help@gcc.gnu.org,
	linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: undefined reference to `__aarch64_cas4_sync' error on arm64
 native build
Message-ID: <ZZ_QaIrlKlFNdDbG@FVFF77S0Q05N>
References: <ZZvS8rigFJR8L56c@FVFF77S0Q05N>
 <fb6c8253fd90e66c036a85954c3299bc2c047473.camel@xry111.site>
 <CAJNi4rPj0Wc7ByqrS-GVLUUEnOFPZi8A5nLLCEEJErqAe16EZw@mail.gmail.com>
 <9aef98eed96ed32962ce90499291cb30ad5e3e14.camel@xry111.site>
 <20240109074843.GI19790@gate.crashing.org>
 <4ee8067e72028b070d92e10fa33ddde3a498cb48.camel@xry111.site>
 <20240109082647.GJ19790@gate.crashing.org>
 <CAJNi4rM_w5JKjug1PtV+tHyk11DUhRJ-K1pSDE6P1x8KSU2wrg@mail.gmail.com>
 <20240110141005.GL19790@gate.crashing.org>
 <CAJNi4rMw1rN64hGZbraoDwtOJOMOumVWL_8iLaCb=TYXAhD2Jg@mail.gmail.com>
Precedence: bulk
X-Mailing-List: linux-kernel@vger.kernel.org
List-Id: <linux-kernel.vger.kernel.org>
List-Subscribe: <mailto:linux-kernel+subscribe@vger.kernel.org>
List-Unsubscribe: <mailto:linux-kernel+unsubscribe@vger.kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAJNi4rMw1rN64hGZbraoDwtOJOMOumVWL_8iLaCb=TYXAhD2Jg@mail.gmail.com>

On Thu, Jan 11, 2024 at 09:42:40AM +0800, richard clark wrote:
> On Wed, Jan 10, 2024 at 10:12 PM Segher Boessenkool
> <segher@kernel.crashing.org> wrote:
> >
> > On Wed, Jan 10, 2024 at 01:59:53PM +0800, richard clark wrote:
> > > A ported driver in linux kernel calls '__sync_val_compare_and_swap',
> >
> > That is a builtin function.  It does not necessarily expand to an actual
> > function call.  aarch64 will typically expand it to inline code.
> >
> native gcc version:
> gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
> cross-compiler gcc version:
> aarch64-linux-gnu-gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
> 
> Interesting, the same '__sync_val_compare_and_swap' in the .c file
> will be 'U __aarch64_cas4_sync' in the .o file compiled by native,
> will be 't __cmpxchg_case_mb_32' in the .o file compiled by
> aarch64-linux-gnu-gcc... don't know what the reason is

The __cmpxchg_case_mb_32() function is kernel code from
arch/arm64/include/asm/cmpxchg.h, so I do not believe that's being generated by
the compiler from __sync_val_compare_and_swap().

Are you certain that's being built from the exact same C file?

Are you able to share the code in question? Where has it come from in the first
place?

Thanks,
Mark.