Date: Fri, 17 May 2013 08:43:47 -0400 From: Warner Losh <imp@bsdimp.com> To: Tim Kientzle <kientzle@freebsd.org> Cc: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: clear_cache and clang (was Re: Git crash on EABI system.) Message-ID: <46D3F1AB-52DC-442D-B777-6B493C20B2B5@bsdimp.com> In-Reply-To: <6FEBBFCD-C698-48E6-B9CA-D9FCB6A5AD5A@freebsd.org> References: <A44A52E5-E878-45CD-B032-F111E5E244BA@freebsd.org> <51949698.80205@thieprojects.ch> <2290084B-D302-4489-BB01-817497901E2B@freebsd.org> <5195F2CA.2090103@thieprojects.ch> <6FEBBFCD-C698-48E6-B9CA-D9FCB6A5AD5A@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On May 17, 2013, at 8:22 AM, Tim Kientzle wrote:
>=20
> On May 17, 2013, at 5:05 AM, Werner Thie wrote:
>=20
>> Tim
>>=20
>> Maybe you or somebody else can shed some light onto how compiler-rt =
is used for the ARM platform, specifically why am I getting a
>>=20
>> missing symbol __clear_cache
>=20
> I suspect it's somehow related to this (from libcompiler_rt/Makefile):
>=20
> # Don't build clear_cache on ARM with clang as it is a builtin there.
> .if ${MACHINE_CPUARCH} !=3D "arm" || ${COMPILER_TYPE} !=3D "clang"
> SRCF+=3D clear_cache
> .endif
>=20
> Do you know what code in ctypes for Python is referring to
> that symbol? There may be some oddity in how that symbol is
> being referenced that's incompatible with the clang built-in.
So why would the compiler type matter for libcompiler_rt?
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46D3F1AB-52DC-442D-B777-6B493C20B2B5>