Date: Fri, 17 May 2013 13:39:27 +0100 From: Andrew Turner <andrew@fubar.geek.nz> 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: <20130517133927.62575abe@bender> 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 Fri, 17 May 2013 08:22:14 -0400
Tim Kientzle <kientzle@freebsd.org> wrote:
>
> On May 17, 2013, at 5:05 AM, Werner Thie wrote:
>
> > Tim
> >
> > 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
> >
> > missing symbol __clear_cache
>
> I suspect it's somehow related to this (from libcompiler_rt/Makefile):
>
> # Don't build clear_cache on ARM with clang as it is a builtin there.
> .if ${MACHINE_CPUARCH} != "arm" || ${COMPILER_TYPE} != "clang"
> SRCF+= clear_cache
> .endif
>
> 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.
__clear_cache is a builtin function in clang and it will complain if
we have a function with it's name because of this.
There may be issues when linking with objects built with gcc, however I
don't know the state of gcc from the ports tree. The only known working
version of gcc for FreeBSD ARM EABI is in base.
Andrew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130517133927.62575abe>