From owner-freebsd-toolchain@freebsd.org Sun Dec 25 18:36:30 2016 Return-Path: Delivered-To: freebsd-toolchain@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9FFA8C90F05 for ; Sun, 25 Dec 2016 18:36:30 +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 6653214F2; Sun, 25 Dec 2016 18:36:30 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from [IPv6:2001:7b8:3a7::e94a:2ec2:906d:514b] (unknown [IPv6:2001:7b8:3a7:0:e94a:2ec2:906d:514b]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id B4D863C5C6; Sun, 25 Dec 2016 19:36:21 +0100 (CET) Content-Type: multipart/signed; boundary="Apple-Mail=_1FBDFFF8-E436-4ECE-B5EB-37FCEB0E86FD"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: status of WITH_SHARED_TOOLCHAIN From: Dimitry Andric In-Reply-To: <73e81366-b932-053e-aebf-f8eaebd8ab5a@FreeBSD.org> Date: Sun, 25 Dec 2016 19:36:15 +0100 Cc: freebsd-toolchain@freebsd.org Message-Id: References: <73e81366-b932-053e-aebf-f8eaebd8ab5a@FreeBSD.org> To: Nikolai Lifanov X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.23 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, 25 Dec 2016 18:36:30 -0000 --Apple-Mail=_1FBDFFF8-E436-4ECE-B5EB-37FCEB0E86FD Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii On 25 Dec 2016, at 19:21, Nikolai Lifanov wrote: > > I would like to understand why WITH_SHARED_TOOLCHAIN is not the default. This has been a long standing tradition. Mainly, because you could theoretically rescue yourself out of some bad situations by being able to compile yourself out of it, since statically linked executables won't break if e.g. libc.so or ld-elf.so is screwed up. This is also the reason that /sbin/init and /rescue/rescue are statically linked. Additionally, it could give a minor performance improvement, that is if the slowdown caused by dynamic linking is not offset by reading a larger executable. > My Raspberry Pi 3 is self-hosting with -j4 and doesn't run out of memory > if the toolchain is shared. Is there a downside to this option? I normally always use WITH_SHARED_TOOLCHAIN, and I have yet to encounter any problem with it. -Dimitry --Apple-Mail=_1FBDFFF8-E436-4ECE-B5EB-37FCEB0E86FD Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.30 iEYEARECAAYFAlhgEaUACgkQsF6jCi4glqNo8QCdEzzB0I95lZhBuB/H8GtpaV3P u2gAnRolVXSlMDLAoZ1MO9b2wHKfOXOX =1KT8 -----END PGP SIGNATURE----- --Apple-Mail=_1FBDFFF8-E436-4ECE-B5EB-37FCEB0E86FD--