From owner-freebsd-toolchain@freebsd.org Sun Aug 12 00:05:53 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 14BAD1057162 for ; Sun, 12 Aug 2018 00:05:53 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x22f.google.com (mail-io0-x22f.google.com [IPv6:2607:f8b0:4001:c06::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 99956964F1 for ; Sun, 12 Aug 2018 00:05:52 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x22f.google.com with SMTP id l7-v6so11110948ioj.1 for ; Sat, 11 Aug 2018 17:05:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=seQRXN2ar7mzXI96diYKNoAMUBKsRJdXdy4QPK9RGNE=; b=tlDihPNpnA81bD83sb/l4xpwcybzU1aJSdewdZWHVPPHSNB6PkTgNZgAouQ62sdIit hZ0Na/PpfYqztmS29KN7xK7vUNTHukGzC9vPHR943fhcSGI1slzM4fwli5qLOerS+79S EytHGlQDJffE681oqOM0S14xNr87n6Q6s+bZWTo88KUgfRfSt2iVzzWdZUSj2vZETicI A9328GsY5nizYIkzmMWOORwdy/WA/7xpDR4g3PVg3m3bR5nCg0UNMsgAtjm4snZzbljW KEWtIWyaW1Qj+MbVS/sIOjkINyeWKMpi9NISoSjCYVpDP7zqyhJqIPqo9KcuzU3j68jq yFGA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=seQRXN2ar7mzXI96diYKNoAMUBKsRJdXdy4QPK9RGNE=; b=rSMtkSPlo5SqHwAanWFhj5/oWxy7eeIa6IgUgZdE+DCuu208iDpJfo8jkgAqJppt9w EfaYEFxXlxMfwBARlkZoSRpB5/ojOaS6scmjI68fGbXhnCt+STEAB9ioJMmSZka+Q085 NrHFxOS7ktMsOEAC/2SLwYHz6iC136VA3cORe7iwzC2bKs0vZX5qy2LaPujZn6HjIuEt riND4VkRpxkXr7TWQOzuV/RyoE1m5gCLtgUgrQFDfgIsoYAZahpbZfTwxmG6hkN9UuXj srYe7fYIHOXqxn6R8Alij+bwWs7KAvpV3tr/5m5QfmKipdpliclfncYKmNTdwZZfWe/h f1Qg== X-Gm-Message-State: AOUpUlGmaL62s5YWqXdNnGy+41dHIJjy+plWSts468PVZoFkYu/nPID9 AnE7l8wkK/OLkKcUDVfa/zfL5udjBqusCOXm3PsZT7IAKmE= X-Google-Smtp-Source: AA+uWPwquk8Wnjok1YfW/q3x97dgTiGzYL4N5x7qjPXviRn5XiDrXoBepjBNHKGjXbDXKGm/kL/7rqKnKwHS/uiCnCg= X-Received: by 2002:a6b:f70f:: with SMTP id k15-v6mr2686494iog.37.1534032351776; Sat, 11 Aug 2018 17:05:51 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:381a:0:0:0:0:0 with HTTP; Sat, 11 Aug 2018 17:05:51 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: <8B467E75-A6D3-41A5-8EA1-4DDFE0E14CC5@nexustechnology.com> References: <1880880F-9D9D-47E0-A7A4-5369A3770F89@FreeBSD.org> <8B467E75-A6D3-41A5-8EA1-4DDFE0E14CC5@nexustechnology.com> From: Warner Losh Date: Sat, 11 Aug 2018 18:05:51 -0600 X-Google-Sender-Auth: CWeTSREPuAtoHPM6ryzv92iozS0 Message-ID: Subject: Re: Broken arm support in clang now? To: Mark Millard Cc: Dimitry Andric , "freebsd-toolchain@FreeBSD.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 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: Sun, 12 Aug 2018 00:05:53 -0000 On Sat, Aug 11, 2018 at 1:01 PM, Mark Millard < mark.millard@nexustechnology.com> wrote: > On 2018-Aug-11, at 11:09 AM, Dimitry Andric wrote: > > > > On 11 Aug 2018, at 19:31, Warner Losh wrote: > >> > >> 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: > >>> > >>> From 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. > > ... > > Did the build get either of the below notices? Both? > > make[1]: "/usr/src/Makefile.inc1" line 341: SYSTEM_COMPILER: Determined > that CC=cc matches the source tree. Not bootstrapping a cross-compiler. > This one I have. > make[1]: "/usr/src/Makefile.inc1" line 346: SYSTEM_LINKER: Determined that > LD=ld matches the source tree. Not bootstrapping a cross-linker. > This one I don't. Warner > ? > > (The example text was taken from an amd64 -> aarch64 cross build.) > > >> Host is amd64. Target is arm. No src.conf. Did a full buildworld > TARGET=arm 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... > > > > === > > Mark Millard > Nexus Technology, Inc. > 78 Northeastern Blvd., Unit #2 > Nashua NH 03062 > > 877-595-8116 x821 > > mark.millard@nexustechnology.com > >