To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=108371
                 Issue #|108371
                 Summary|cppu: preserve 128-bit stack alignment on x86 in cpp_u
                        |no/gcc3_linux_intel
               Component|udk
                 Version|OOo 3.1.1
                Platform|PC
                     URL|http://bugs.gentoo.org/show_bug.cgi?id=292519
              OS/Version|Linux
                  Status|UNCONFIRMED
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|PATCH
                Priority|P3
            Subcomponent|code
             Assigned to|kr
             Reported by|ecatmur





------- Additional comments from [email protected] Sat Jan 16 00:20:34 
+0000 2010 -------
The gcc3 linux-intel-x86 ABI expects stack frames to be aligned to 128-bit 
(16-byte) boundaries.  
This is to allow optimised code to use SSE and SSE2 instructions with 128-bit 
operands, which 
segfault when used on (stack) memory operands violating 128-bit alignment.

This is seen at http://bugs.gentoo.org/show_bug.cgi?id=292519 as a segfault 
during installation, 
when executing build/ooo310-m19/solver/310/unxlngi6.pro/bin/regcomp.  The 
optimised code 
where the segfault occurs is in python internals, in PyString_Format.

The issue is that the asm within cpp_uno/gcc3_linux_intel does not preserve 
128-bit stack 
alignment.  gcc3 assumes 128-bit alignment and emits code that preserves that 
alignment, but 
requires that asm also act to preserve alignment.

I attach a patch to preserve alignment in cpp_uno/gcc3_linux_intel.

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to