On 3/17/26 00:42, Antoine Brodin wrote: > On Tue, Mar 17, 2026 at 12:40 AM Philip Paeps <[email protected]> wrote: >> On 2026-03-16 19:18:45 (+0800), Mark Millard wrote: >>> On 3/15/26 21:18, Philip Paeps wrote: >>>> On 2026-03-13 21:53:48 (+0800), Olivier Certner wrote: >>>>> You are likely hitting a known problem, see thread "performance >>>>> regressions in 15.0". E.g., just picked one mail saying what I >>>>> also >>>>> personally think about it: >>>>> https://lists.freebsd.org/archives/freebsd-current/2025- >>>>> December/009623.html >>>>> (arguably, some RAM factories have burnt out for retail consumers >>>>> since then...) >>>>> >>>>> AFAIK, the default was never switched back, but if you're building >>>>> from source, a new knob was added to recover the previous behavior, >>>>> see: >>>>> https://cgit.freebsd.org/src/commit/?id=8d5a11cd0137d3ad >>>> >>>> Does this affect the package builders? >>> >>> Yes for the 15.* jails, the main jails [so: 16.0], and the future >>> 14.4+ >>> jails. >>> >>> (The 13.5 jails and the 14.3 jails do not have the problem.) >>> >>>> Does that build fix go in the >>>> host or in the build jails? >>> >>> What primarily matters is how the world put in the build-jail was >>> built. >> >> pkgmgr controls the build jails. I don't think they use clusteradm >> images in the jails. We only supply the host operating system. > > We use default releases (or security updates of default releases)
So no potential WITH_LLVM_LINK_STATIC_LIBRARIES based updates for 14.* or 15.* builder jails until 15.1 and 14.5 . What about for main's builder jails (so: no releases, ampere2 and beefy24 builder systems as stands)? It would be interesting to see how much of a difference WITH_LLVM_LINK_STATIC_LIBRARIES use makes for ampere2 and its 230+ hr port-package builds (the longest as stands). As far as I can tell, WITH_LLVM_LINK_STATIC_LIBRARIES use would not hurt main being a debug testing context. > > Antoine > > -- === Mark Millard marklmi at yahoo.com
