Date: Mon, 12 Jul 2021 17:01:37 +0000 From: bugzilla-noreply@freebsd.org To: multimedia@FreeBSD.org Subject: [Bug 257124] multimedia/ffmpeg: Fails to link: ld: error: inline assembly requires more registers than available at line [on i386 with LTO option] Message-ID: <bug-257124-12827-xoyV6iLZid@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-257124-12827@https.bugs.freebsd.org/bugzilla/> References: <bug-257124-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=3D257124 --- Comment #10 from Mikhail Teterin <mi@FreeBSD.org> --- > The problem is that once you start inlining It is my understanding, that "inline" is a hint (as is/was "register")... If compiler knows, the target architecture cannot handle it, it will/should sk= ip it. > Perhaps, although I suspect there will not be a lot of interest Ok, so we agree, that it is a clang/llvm bug and what's left is to figure o= ut, what to do about it. > investigating i386-specific optimization issues Sad... i386 is still listed as Tier-1 in 11. and 12., becoming Tier-2 in 13. https://www.freebsd.org/platforms/ I wonder, what LLVM's stance on this is. > I believe it is disabled by default on all archs right now? Yes, it is, you're right. I'd say, it can be enabled by default, where know= n to work, and marked with warning elsewhere. But not REMOVED altogether. > I'm sure nobody will use an ancient i386 only machine There are valid reasons to use i386 even on modern processors -- such as, f= or example, as a small-memory (under 4Gb) VM in a large (64-bit) host. --=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-257124-12827-xoyV6iLZid>