From owner-freebsd-toolchain@freebsd.org Thu Aug 16 14:16:28 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 C870B1067892 for ; Thu, 16 Aug 2018 14:16:28 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x22a.google.com (mail-it0-x22a.google.com [IPv6:2607:f8b0:4001:c0b::22a]) (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 54CF184A49 for ; Thu, 16 Aug 2018 14:16:28 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x22a.google.com with SMTP id d70-v6so20394051ith.1 for ; Thu, 16 Aug 2018 07:16:28 -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=DzRZcP09QhtBcML7BJ8+KCfpUjPqBltlq0ubqS2r8aY=; b=uu3ppElSQ5W4GOvYNLArdSDCPf6yxizmmZivaXj9SJEt3BxrljeRllt2rG6iNUdoqt coA7Jcx+4LXNEi5r0QmvktNrgzuVp4/iYy6ktbb8lOFPYYvVn6zVXeieGdzeg2iCtI28 B4fY4Jiph6I12SwHfLhUqfKBzsk7FWOjSRVPK1wEOY25n3/pZ39XGGBtK9Dj8IpHhklx DKRBmTKvHXWLZX+X2bIw9mR19xinxwRcX+SmFk+ecQe87Q8914lI+e46DSp+XlHtL8+2 A5AwSmX6UdBtFz4r57BwG1TXt9QFkdG9wAC7/6lfdnjDB+CfDWpOCDASHa24RjZ2erCd APHA== 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=DzRZcP09QhtBcML7BJ8+KCfpUjPqBltlq0ubqS2r8aY=; b=P9kkyJYcm6kAeTIqa0AdCdvZ1kMwvF7w9b9SgRNp5iNAZgg5L0O63/kiCaOrRHzTcG j5oJGtdNCtTH7m9nT93Orex5VuLU9m3jVjWx2KN8kcNOerV4UTEU7Cn1+BZOYqco/m9C bfMQBRft/hHdFK/AU20VNnRQU2Sj9clT5oo5ag08Oofj1tIbk976k1Gt+CmBx3zD2kKg IwDhb4YxRtMt/81Quzqh+fKN5YjWMx5yZakJbrKRtBtKtQOGMkCXE2PW39idvxwb929r IiCoXGyDeuGDujJ9Lcg57sEoIWdH9BYDi+X2mXwtaS/6LxbH1cvlbzsVtkDtkZqyYNgR f4wA== X-Gm-Message-State: AOUpUlE/t1yozIqcQEf4vlRHcz+P8nOwZEwbh5vvMEr4g/RQjJCSSs4J YA22DxU5D8pOLZR0ZrZUuhZcYvEcaEcRW3bA1IKMSg== X-Google-Smtp-Source: AA+uWPyfYsqntIgnVALNLtaLPHUI9uhfLneqL5u/1HX4mMLApwzZuoq602cu8L8rzmsD6VEvKsYnTVaLDJrKiRYq8Bs= X-Received: by 2002:a24:d2:: with SMTP id 201-v6mr689370ita.60.1534428987473; Thu, 16 Aug 2018 07:16:27 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:257:0:0:0:0:0 with HTTP; Thu, 16 Aug 2018 07:16:26 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: <86844298-1268-4F5E-A6CD-64CADC022FB9@yahoo.com> References: <1880880F-9D9D-47E0-A7A4-5369A3770F89@FreeBSD.org> <8B467E75-A6D3-41A5-8EA1-4DDFE0E14CC5@nexustechnology.com> <230C1E7D-04DB-4E45-8A40-F6B2F5E557E9@yahoo.com> <86844298-1268-4F5E-A6CD-64CADC022FB9@yahoo.com> From: Warner Losh Date: Thu, 16 Aug 2018 08:16:26 -0600 X-Google-Sender-Auth: eIub7GamJo1LSBN-v4LnID9ugXg Message-ID: Subject: Re: Broken arm support in clang now? To: Mark Millard Cc: Ed Maste , "freebsd-toolchain@FreeBSD.org" , Dimitry Andric 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: Thu, 16 Aug 2018 14:16:29 -0000 On Thu, Aug 16, 2018 at 8:14 AM, Mark Millard wrote: > On 2018-Aug-16, at 6:38 AM, Ed Maste wrote: > > > On 11 August 2018 at 20:45, Mark Millard via freebsd-toolchain > > wrote: > >> > >> Is the link command itself available? (The .../sys/*/kernel.full.meta > >> likely has it if it is still around.) > > > > I tried a tinderbox build right now and saw the lld warnings from > > linking zfs.ko. It appears to be fallout from the change to build > > clang and lld only once for tinderbox, because we're invoking ld from > > the ${HOST_TARGET} path: > > > > /scratch/tmp/emaste/obj/scratch/tmp/emaste/freebsd/ > freebsd11-amd64/tmp/usr/bin/ld > > -m armelf_fbsd -Bshareable -znotext -d -warn-common --build-id=sha1 > > -o zfs.ko.full zfs.kld > > /scratch/tmp/emaste/obj/scratch/tmp/emaste/freebsd/ > freebsd11-amd64/tmp/usr/bin/ld: > > warning: lld uses extended branch encoding, no object with > > architecture supporting feature detected. > > /scratch/tmp/emaste/obj/scratch/tmp/emaste/freebsd/ > freebsd11-amd64/tmp/usr/bin/ld: > > warning: lld may use movt/movw, no object with architecture supporting > > feature detected. > > So ld.lld is not a valid cross linker for some arm variants? A > architecture specific bootstrap one is needed? > > Is this because armelf_fbsd is not specific enough to > identify the accurate target emulation? Is it because > the .o's are not sufficient for that identification? > > Note: I got the questions from reading the output in: > > # ld.lld > ld.lld: error: no input files > ld.lld: error: target emulation unknown: -m or at least one .o file > required > > So it appears that -m and/or .o's are used to identify targets. > I'm not clear on the criteria when both are present. > > (ld.lld does not take -target as an argument.) lld uses instructions and features introduced in armv7 unconditionally to do its linking. The bug appears to be that clang invokes it unconditionally in some cases. Warner