svn commit: r353937 - in head/share: man/man5 mk

[Alexey Dokuchaev]

On Wed, Oct 23, 2019 at 11:31:41AM -0700, Enji Cooper wrote:
> > On Oct 23, 2019, at 10:02, Dimitry Andric <dim at freebsd.org> wrote:
> > New Revision: 353937
> > URL: https://svnweb.freebsd.org/changeset/base/353937
> > 
> > Log:
> >  Build toolchain components as dynamically linked executables by default

What are the benefits of the new order?

> >  Summary:
> >  Historically, we have built toolchain components such as cc, ld, etc as
> >  statically linked executables.  One of the reasons being that you could
> >  sometimes save yourself from botched upgrades, by e.g. recompiling a
> >  "known good" libc and reinstalling it.

> >  In this day and age, we have boot environments, virtual machine
> >  snapshots, cloud backups, and other much more reliable methods to
> >  restore systems to working order.  So I think the time is ripe to flip

What about those of us who cannot use BEs, VMs, and other "cloudy" tech
because, well, they might not work as well and reliably as one might think?

> Using dynamic binaries instead of static binaries might actually regress
> performance in a way you don't expect, depending on -j values, etc. Static
> binaries avoid the dynamic linker, which (obviously) results in a perf hit
> at scale [...]

Very good point.

> Did you calculate the perf trade offs for the static binaries at low -j vs
> high -j, system and user time, etc?

I'd like to know the answer to this question (and the results) as well.

./danfe