Date: Thu, 07 Nov 2019 15:18:15 +0000 From: bugzilla-noreply@freebsd.org To: toolchain@FreeBSD.org Subject: [Bug 233664] enable LLVM libunwind for armv7, armv6 Message-ID: <bug-233664-29464-2KucnfNj87@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-233664-29464@https.bugs.freebsd.org/bugzilla/> References: <bug-233664-29464@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=3D233664 Conrad Meyer <cem@freebsd.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Closed Summary|enable LLVM libunwind for |enable LLVM libunwind for |armv7, armv6, arm |armv7, armv6 Resolution|--- |FIXED --- Comment #4 from Conrad Meyer <cem@freebsd.org> --- Ah, sorry for duplicating work. I wasn't aware of this PR. Yeah, there were a couple problems here. The unwind-ehabi-helpers.h file j= ust produced conflicts with existing definitions. There are at least two diffe= rent variants of unwind.h in our tree, and different portions gcc_personality_v0 build with different headers. Like comment 2 suggests, I added the extra GCC 3.5 symbols to ARM only using Symbol.map. And as the description suggests, we needed those 3 other symbo= ls as well. No one has complained yet, afaik, but I haven't checked my email = yet this morning. I think we can drop 'arm' from the Summary and resolve this, given it's on = the chopping block for 2020. --=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-233664-29464-2KucnfNj87>