Date: Mon, 23 May 2011 21:48:40 +0200 From: Dimitry Andric <dim@FreeBSD.org> To: Mark Linimon <linimon@lonesome.com> Cc: svn-src-head@freebsd.org, Roman Divacky <rdivacky@freebsd.org>, src-committers@freebsd.org, svn-src-all@freebsd.org Subject: Re: svn commit: r222183 - head/lib/clang Message-ID: <4DDABA18.2000901@FreeBSD.org> In-Reply-To: <20110522213058.GB21144@lonesome.com> References: <201105221632.p4MGWjUb081825@svn.freebsd.org> <20110522202256.GA43412@freebsd.org> <20110522213058.GB21144@lonesome.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2011-05-22 23:30, Mark Linimon wrote: > On Sun, May 22, 2011 at 10:22:56PM +0200, Roman Divacky wrote: >> The problem here is deeper in my opinion. What FreeBSD calls >> amd64 the rest of the world (ie. linux) calls x86_64, I think >> that instead of this we should teach llvm/clang about "amd64". >> Maybe as a FreeBSD-only diff. > > If we move away from "amd64", we are going to need a _substantial_ amount > of work on ports. Note, this commit was *only* to set clang's compiled-in default arch on amd64, to make sure clang selects the correct target CPU when it generates code. This should not influence too many configure scripts, unless they foolishly grep around in "$CC -v" output... ;)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4DDABA18.2000901>