Martin Blapp a000e73aee Depending on how a compiler generates code (e.g., GCC 3.2.2 vs. GCC ... 3.0.1), a bug in the gcc3_linux_intel UNO bridge is revealed: If a C/C++ function returns a complex object (class, struct, union), the 386 ABI specifies that the caller pushes the address for that object on the stack, and the callee removes it from the stack. The code in the UNO bridge (callVirtualMethod in bridges/source/cpp_uno/gcc3_linux_intel/uno2cpp.cxx) erroneously assumes that the callee does *not* remove the address from the stack, corrupting the stack. We use the same bridge code as linux does for gcc3.x. So this fix also works for us. Submitted by: Stephan Bergmann <stephan.bergmann@sun.com>		2003-03-27 22:13:25 +00:00
..
files	Depending on how a compiler generates code (e.g., GCC 3.2.2 vs. GCC	2003-03-27 22:13:25 +00:00
distinfo	Update to a 20030324 snapshot. Remove a old unused	2003-03-27 09:39:00 +00:00
Makefile	OOo1.1 seems to link against a lib in the jdk. OOo will still run	2003-03-27 09:41:44 +00:00
pkg-descr	First step towards a working port.	2002-02-28 23:36:03 +00:00
pkg-message	First step to make this port working. Configure works and all patches	2002-10-18 22:41:42 +00:00
pkg-plist	First step to make this port working. Configure works and all patches	2002-10-18 22:41:42 +00:00