Firefox 138 port does not use parallel LTO

drsnx60

drsnx60

HI I noticed that while port www/ungoogled-chromium does use parallell LTO linking , port www/firefox does not.
the LTO single threaded linking on Firefox port takes 5 times longer then the parallel LTO linking on ungoogled-chromium.
4 minutes for chromium and 20 minutes for firefox using a I7-13700K CPU.
 
drsnx60 said:
HI I noticed that while port www/ungoogled-chromium does use parallell LTO linking , port www/firefox does not.
the LTO single threaded linking on Firefox port takes 5 times longer then the parallel LTO linking on ungoogled-chromium.
4 minutes for chromium and 20 minutes for firefox using a I7-13700K CPU.
Click to expand...
Code: 
Configuration Options:
    ===> The following configuration options are available for firefox-139.0,2:
         CANBERRA=off: Sound theme alerts
         DBUS=on: D-Bus IPC system support
         DEBUG=off: Build with debugging support
         FFMPEG=on: FFmpeg support (WMA, AIFF, AC3, APE...)
         LIBPROXY=off: Proxy support via libproxy
         LTO=off: Use Link-Time Optimization
         OPTIMIZED_CFLAGS=on: Use extra compiler optimizations
         PROFILE=on: Build with profiling support
         TEST=off: Build and/or run tests
    ====> Extra cubeb audio backends (OSS is always available)
         ALSA=off: ALSA audio architecture support
         JACK=on: JACK audio server support
         PULSEAUDIO=on: PulseAudio sound server support
         SNDIO=on: Sndio audio support
    ===> Use 'make config' to modify these settings
 
I just built the current ESR version (128.11.0_1) with LTO enabled. Bulid succeeds and ~43mins isn't terribly far from builds with -LTO (~32mins during the last 'poudriere bulk' with other ports building at the same time), so I guess at least for ESR it's still doing everything in parallel?
 
firefox-esr and waterfox are currently building on my buildhost and only a single lld process running for each of them that both top out at 100% CPU (i.e. a single core).
 
aaaand it's broken again.
Building firefox-esr-128.11.0_1,1 from latest on 14.3-RELEASE with LTO=on fails with linker error...
Possibly related to the new rust version (1.87) which also fails to build on first attempt (needed 2-3 attempts to get it built on all build hosts... first try always gets interrupted after extracting for >1h (poudriere has its own zfs pool on nvme on all those hosts...), then it just errors out at completely random points until it finally succeeds to build. (I guess just like the >35GB TMPFS and >64GB RAM required for building it, this may also be considered "normal" by rust devs)

edit: www/waterfox and www/ungoogled-chromium also fail with linker errors - so it's definitely a regression with the new rust version. (on quarterly all 3 still build fine with LTO=on)
 
Agree that after upgrading to Rust 1.87 building Firefox 139.0.4 with LTO option fails with LLD error .
Need to build without LTO ( Link time optimization )
Probably Rust 1.87 and CLANG 19.1.7 dont agree on how to do it.
 
You must log in or register to reply here.
Back
Top