Date: Wed, 09 Mar 2022 17:26:19 +0000 From: bugzilla-noreply@freebsd.org To: office@FreeBSD.org Subject: [Bug 262008] editors/libreoffice failed to build Message-ID: <bug-262008-25061-GMOshD04d1@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-262008-25061@https.bugs.freebsd.org/bugzilla/> References: <bug-262008-25061@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=3D262008 --- Comment #55 from commit-hook@FreeBSD.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=3D72df847a94bccee245a3316e4f848482b= 9ac2ac2 commit 72df847a94bccee245a3316e4f848482b9ac2ac2 Author: Dimitry Andric <dim@FreeBSD.org> AuthorDate: 2022-03-08 21:53:16 +0000 Commit: Dimitry Andric <dim@FreeBSD.org> CommitDate: 2022-03-09 17:25:18 +0000 Remove compat hacks from libcxxrt's _Unwind_Exception This reverts 9097e3cbcac4, which was in itself a revert of upstream libcxxrt commits 88bdf6b290da ("Specify double-word alignment for ARM unwind") and b96169641f79 ("Updated Itanium unwind"), and a reapplication of our commit 3c4fd2463bb2 ("libcxxrt: add padding in __cxa_allocate_* to fix alignment"). The editors/libreoffice port will be patched to be able to cope with the standards-compliant alignment of _Unwind_Exception and consequently, that of __cxa_exception. The layouts and sizes of these structures should then be completely the same for libcxxrt, libunwind and libc++abi. PR: 262008 Reviewed by: emaste, jhb, theraven MFC after: 3 days Differential Revision: https://reviews.freebsd.org/D34488 contrib/libcxxrt/exception.cc | 30 ++++++------------------------ contrib/libcxxrt/unwind-arm.h | 2 +- contrib/libcxxrt/unwind-itanium.h | 9 ++++++--- 3 files changed, 13 insertions(+), 28 deletions(-) --=20 You are receiving this mail because: You are on the CC list for the bug. 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-262008-25061-GMOshD04d1>