Date: Sat, 03 Jun 2023 11:36:51 +0000 From: bugzilla-noreply@freebsd.org To: multimedia@FreeBSD.org Subject: [Bug 271798] multimedia/ffmpeg: Enable LTO by default on aarch64 and amd64 Message-ID: <bug-271798-12827-YnmUeW3AYg@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-271798-12827@https.bugs.freebsd.org/bugzilla/> References: <bug-271798-12827@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D271798 --- Comment #2 from Jan Beich <jbeich@FreeBSD.org> --- If LTO has placebo benefit then the port option should be removed in favor = of WITH_LTO via Mk/Features/lto.mk e.g., to reduce maintenance. LTO isn't safe with mixed alignment (e.g., in dav1d) or mixed toolchain (LLVM bitcode vs. = GCC GIMPLE when using static libraries) but I didn't notice issues when dogfood= ing LTO in ffmpeg. Examples documenting statistical difference: - ports d4e1f93dbb3a (svt-av1) - ports 32c2b95c682e (libjxl) - ports 501e1ed88f97 (foot) However, ports 55006395d27c (mesa-devel) and ports 6ec985b72d58 (firefox) relied on upstream benchmarks. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-271798-12827-YnmUeW3AYg>