From owner-freebsd-current@freebsd.org Tue Aug 21 20:29:45 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 86D8D107E7FF for ; Tue, 21 Aug 2018 20:29:45 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: from spindle.one-eyed-alien.net (spindle.one-eyed-alien.net [199.48.129.229]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 31AC595339; Tue, 21 Aug 2018 20:29:45 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: by spindle.one-eyed-alien.net (Postfix, from userid 3001) id 333015A9F13; Tue, 21 Aug 2018 20:29:44 +0000 (UTC) Date: Tue, 21 Aug 2018 20:29:44 +0000 From: Brooks Davis To: Dimitry Andric Cc: "Rodney W. Grimes" , blubee blubeeme , FreeBSD Current , Brooks Davis Subject: Re: building LLVM threads gets killed Message-ID: <20180821202944.GB83826@spindle.one-eyed-alien.net> References: <201808201426.w7KEQo9j074809@pdx.rh.CN85.dnsmgr.net> <4ECEE41C-E1FF-4B6A-A138-3BDDB6552A7D@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="FkmkrVfFsRoUs1wW" Content-Disposition: inline In-Reply-To: <4ECEE41C-E1FF-4B6A-A138-3BDDB6552A7D@FreeBSD.org> User-Agent: Mutt/1.9.4 (2018-02-28) 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: Tue, 21 Aug 2018 20:29:45 -0000 --FkmkrVfFsRoUs1wW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Aug 20, 2018 at 07:33:32PM +0200, Dimitry Andric wrote: > On 20 Aug 2018, at 16:26, Rodney W. Grimes wrote: > >=20 > >> On 20 Aug 2018, at 05:01, blubee blubeeme wrote: > >>>=20 > >>> I am running current compiling LLVM60 and when it comes to linking > >>> basically all the processes on my computer gets killed; Chrome, Firef= ox and > >>> some of the LLVM threads as well > ... > >=20 > >> It is running out of RAM while running multiple parallel link jobs. If > >> you are building using WITH_DEBUG, turn that off, it consumes large > >> amounts of memory. If you must have debug info, try adding the > >> following flag to the CMake command line: > >>=20 > >> -D LLVM_PARALLEL_LINK_JOBS:STRING=3D"1" > >>=20 > >> That will limit the amount of parallel link jobs to 1, even if you > >> specify -j 8 to gmake or ninja. > >>=20 > >> Brooks, it would not be a bad idea to always use this CMake flag in the > >> llvm ports. :) > >=20 > > And this may also fix the issues that all the small > > memory (aka, RPI*) buliders are facing when trying > > to do -j4? >=20 > Possibly, as linking is usually the most memory-consuming part of the > build process (and more so, if debugging is enabled). Are there build > logs available somewhere for those RPI builders? >=20 > 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. -- Brooks --FkmkrVfFsRoUs1wW Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJbfHY3AAoJEKzQXbSebgfA0+8H/2/Q593VOg1Z5wCWTFd2cKtv joOCb1KbhGLQ+BZjsecFAtCtmPXZOrsHZLPq/7+moC1iGFNMLZkLK5S0HvZgvw0Q qnFj07YS4hdYazBUejuykG0WXphLh8p3kl0fwTANixGxGRNwAtaboIhy1NeuR36Y oog61CGsAr+1WOLewpL7EvdaTi3k5ndrkZZIrnvTf66SIxQoCUflQJoFYpdhFvu/ TKcmraerENj+xqu73saEJ5pOBOB+EllV1q60V7QCVlvKpFKokcbRkpJqbVWdh3JT p3iq98U15/IHvyVpFQlpescYTby/RxN5mzt+5kF3mEGUGwbs3VMgXCeE9ExA/gk= =dmt8 -----END PGP SIGNATURE----- --FkmkrVfFsRoUs1wW--