From owner-freebsd-toolchain@freebsd.org Sat Aug 11 18:09:41 2018 Return-Path: Delivered-To: freebsd-toolchain@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EE45C1075C84 for ; Sat, 11 Aug 2018 18:09:40 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "tensor.andric.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8C0938BE33; Sat, 11 Aug 2018 18:09:40 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from coleburn.home.andric.com (coleburn.home.andric.com [192.168.0.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 0BEA1398F8; Sat, 11 Aug 2018 20:09:39 +0200 (CEST) From: Dimitry Andric Message-Id: Content-Type: multipart/signed; boundary="Apple-Mail=_1656EDE9-A3AF-40A9-9ED3-F32B410C8EE0"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: Broken arm support in clang now? Date: Sat, 11 Aug 2018 20:09:35 +0200 In-Reply-To: Cc: "freebsd-toolchain@FreeBSD.org" , Ed Maste To: Warner Losh References: <1880880F-9D9D-47E0-A7A4-5369A3770F89@FreeBSD.org> X-Mailer: Apple Mail (2.3445.9.1) X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Aug 2018 18:09:41 -0000 --Apple-Mail=_1656EDE9-A3AF-40A9-9ED3-F32B410C8EE0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 11 Aug 2018, at 19:31, Warner Losh wrote: >=20 > On Sat, Aug 11, 2018, 10:20 AM Dimitry Andric wrote: > On 11 Aug 2018, at 16:55, Warner Losh wrote: > > > > It looks like armv5 clang bogusly uses lld: > > > > =46rom a 'make buildkernel' of the RT1310 kernel config: > > > > cc -target arm-gnueabi-freebsd12.0 ... > > ld: warning: lld uses extended branch encoding, no object with = architecture > > supporting feature detected. > > ld: warning: lld may use movt/movw, no object with architecture = supporting > > feature detected. ... > Host is amd64. Target is arm. No src.conf. Did a full buildworld = TARGET=3Darm a few days ago. /usr/bin/ld is lld. Okay, so in the above "cc" command, can you somehow figure out which cc executable it is using? And please add a -v to the "linking kernel.full" command line, so it shows exactly which linker it runs? I have the idea that it is preferring your /usr/bin/ld over ${WORLDTMP}/usr/bin/ld... -Dimitry --Apple-Mail=_1656EDE9-A3AF-40A9-9ED3-F32B410C8EE0 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.2 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCW28mXwAKCRCwXqMKLiCW ozSSAJ9/27UH43a4KKYBDCCE+u31E5zRoACgvexE20zB0bLdaOWmAUOspP26/DQ= =jT4K -----END PGP SIGNATURE----- --Apple-Mail=_1656EDE9-A3AF-40A9-9ED3-F32B410C8EE0--