mmmm....looking at the solari_intel sources, uno2cpp.cxx already contains code similar
to the patch you pointed:
using namespace ::com::sun::star::uno;
namespace
{
static void __attribute__((noinline)) callVirtualMethod(
void * pAdjustedThisPtr,
sal_Int32 nVtableIndex,
void * pRegisterReturn,
typelib_TypeClass eReturnType,
sal_Int32 * pStackLongs,
sal_Int32 nStackLongs )
{
....
....
and
asm volatile (
"mov %%esp, %2\n\t"
// preserve potential 128bit stack alignment
"and $0xfffffff0, %%esp\n\t"
"mov %3, %%eax\n\t"
"lea -4(,%%eax,4), %%eax\n\t"
"and $0xf, %%eax\n\t"
"sub $0xc, %%eax\n\t"
...
...
...
without the need for a new callvirtualmethod.cxx
The remaining part of the patches actually just take out an unused call (dummy_can_throw_anything)
and add some throw() around.
How can we track if that solar files are already taking into account gcc 4.7?
----------------------------------------------------------------------------------
Da: Stephan Bergmann
A: libreoffice@lists.freedesktop.org
Data: 16 febbraio 2015 13.38.47 CET
Oggetto: Re: uno.bin core dump during build
On 02/16/2015 11:38 AM, Gabriele Bulfon wrote:
while building on XStreamOS / illumos, looks like uno.bin gets corrupted
then causing a core dump at first build usage.
Most likely bridges/source/cpp_uno/gcc3_solar_intel/ needs the
equivalent of
"Make cpp_uno/gcc3_linux_x86-64 bridge work with GCC 4.7."
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.