Date: Wed, 08 Jan 2020 08:49:51 +0000 From: bugzilla-noreply@freebsd.org To: toolchain@FreeBSD.org Subject: [Bug 233664] enable LLVM libunwind for armv7, armv6 Message-ID: <bug-233664-29464-M9lA4s9TH5@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-233664-29464@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233664 Michal Meloun <mmel@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|Open |Closed --- Comment #21 from Michal Meloun <mmel@FreeBSD.org> --- (In reply to Conrad Meyer from comment #19) Well, the reality is that your commit broke ABI and many ports (rustc for example but not only) for armv7 (and the following made it worse). So it was "unusable" and "broken". Using your words, next time I would appreciate you to test your commits properly. >From arm64 case, I'm afraid I mistaken the llvm implementation of libunwind with that from devel/libunwind. libunwind from this port will compiles itself, but many dependent ports will not. It exposes gcc-specific macros (a local variable in a named register) that is not used when compiling the library itself, but used by other parties. Did this looks like a humor for you? Be honest, we are both people and we both have the right to make a mistake from time to time. (and the truth is, as my age grows, "from time to time" gets shorter and shorter). I'm closing this bug. -- You are receiving this mail because: You are on the CC list for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-233664-29464-M9lA4s9TH5>