Date: Fri, 14 Apr 2017 23:35:00 +0200 From: Dimitry Andric <dimitry@andric.com> To: Mark Millard <markmi@dsl-only.net> Cc: FreeBSD Toolchain <freebsd-toolchain@freebsd.org> Subject: Re: WITH_LLD_IS_LD vs default WITHOUT_SYSTEM_COMPILER: What are the reasons? Message-ID: <7DB9F23E-2D55-44C3-AA91-C209BF584C4A@andric.com> In-Reply-To: <B7BEE165-C4AC-4670-9972-B9CB522A25DC@dsl-only.net> References: <B7BEE165-C4AC-4670-9972-B9CB522A25DC@dsl-only.net>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On 14 Apr 2017, at 22:40, Mark Millard <markmi@dsl-only.net> wrote: > > man src.conf (from -r315914 ) reports: > > WITH_LLD_IS_LD > Set to use LLVM's LLD as the system linker, instead of GNU > binutils ld. > > This is a default setting on arm64/aarch64. When set, these > options are also in effect: > > WITHOUT_SYSTEM_COMPILER (unless WITH_SYSTEM_COMPILER is set > explicitly) > > I'm curious about: > > A) Why there is a bias to avoid the system compiler? These are just the defaults, detected by the script that generates src.conf.5. The setting of MK_SYSTEM_COMPILER is actually dependent on the host, so it's technically incorrect to have src.conf.5 mention that it is off by default. > and by contrast: > > B) What sort of context justifies explicitly setting > WITH_SYSTEM_COMPILER when WITH_LLD_IS_LD is in use? The settings are mostly orthogonal. MK_SYSTEM_COMPILER was created to avoid building a bootstrap compiler, if the system (host) compiler is new enough. At some point you could also image a MK_SYSTEM_LINKER setting, which would avoid building the bootstrap linker, if the system linker is new enough. -Dimitry [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.30 iEYEARECAAYFAljxQIkACgkQsF6jCi4glqN7jwCgzOzQK+lzSzcmbTPijcqe3qiu GRMAnA9dg08iVxz+kA28nvSaU8cI4Nsd =csZi -----END PGP SIGNATURE-----help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7DB9F23E-2D55-44C3-AA91-C209BF584C4A>