Date: Tue, 26 Mar 2024 18:45:56 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 277333] Mk/Features/lto.mk: passing -C lto=no breaks LTO_UNSAFE ports Message-ID: <bug-277333-7788-GJoh31iAmg@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-277333-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-277333-7788@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=3D277333 --- Comment #18 from Jan Beich <jbeich@FreeBSD.org> --- (In reply to Gleb Popov from comment #16) USES=3Dcargo is not supposed to desync cargo vs. rustc, leading to an undef= ined behavior. If a Rust feature is exposed via Cargo then use Cargo variables to control it. Passing -C lto=3Dno leads to some files built with LTO and some without LTO, likely causing rustc to leak LLVM bitcode (skipping optimizati= on step) to the system linker (LTO-unaware or incompatible LLVM version). See also review D29548 which tried to move rustc bits into a separate USES. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-277333-7788-GJoh31iAmg>