From owner-freebsd-current@freebsd.org Wed Aug 22 10:52:55 2018 Return-Path: Delivered-To: freebsd-current@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 EE6761084ED3 for ; Wed, 22 Aug 2018 10:52:54 +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 8C2F68EA2B for ; Wed, 22 Aug 2018 10:52:54 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from [192.168.1.32] (ip-213-127-237-35.ip.prioritytelecom.net [213.127.237.35]) (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 593783A04F; Wed, 22 Aug 2018 12:52:53 +0200 (CEST) From: Dimitry Andric Message-Id: Content-Type: multipart/signed; boundary="Apple-Mail=_1F225774-3A61-47BD-9CE3-22B7D08CC4DE"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: building LLVM threads gets killed Date: Wed, 22 Aug 2018 12:52:45 +0200 In-Reply-To: <0846E103-2DCC-421F-B82B-1BE287002468@yahoo.com> Cc: FreeBSD Current To: Mark Millard References: <0846E103-2DCC-421F-B82B-1BE287002468@yahoo.com> X-Mailer: Apple Mail (2.3445.9.1) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Aug 2018 10:52:55 -0000 --Apple-Mail=_1F225774-3A61-47BD-9CE3-22B7D08CC4DE Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii On 22 Aug 2018, at 04:01, Mark Millard wrote: > > Brooks Davis brooks at freebsd.org wrote on > Tue Aug 21 20:29:45 UTC 2018 : > >> On Mon, Aug 20, 2018 at 07:33:32PM +0200, Dimitry Andric wrote: >>> . . . >>> >>> I have attached a patch for most of the llvm ports, which sets the >>> LLVM_PARALLEL_LINK_JOBS CMake flag during the configure phase. >> >> Committed in r477756. >> > > lld itself has --threads (default) and --no-threads > (non-default, single threaded link). (Mark Johnston > recently made me aware of this.) In my quick experiment > in just one context, --threads used 5 or so threads > in the lld process. (Likely helps with speed when > the hardware threads are simply available without > conflicts.) > > Does LLVM_PARALLEL_LINK_JOBS contribute to which of > these is in use? No, it just controls how many link processes ninja starts in parallel. If those link processes use threads, like lld does by default, it is outside the control of ninja. Note that lld uses threads to speed up linking, but it might use more memory, so you could turn it off if you are memory constrained. -Dimitry --Apple-Mail=_1F225774-3A61-47BD-9CE3-22B7D08CC4DE 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 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCW31AfQAKCRCwXqMKLiCW oyt/AJ4kqoLdR1ZusuitzPa+oiQ6+nBncwCfdocDvjVJBqGTkVdnQ/mT3wFZ2Hc= =JDep -----END PGP SIGNATURE----- --Apple-Mail=_1F225774-3A61-47BD-9CE3-22B7D08CC4DE--