About openoffice linux/mips porting
Dear all,
Someone(Sunil Amitkumar Jank) is trying to make my old patches for linux/mips OOo into openoffice.org tree, might be some of your gurus can help to have a look at the most important part: the bridge code. It is available at
http://qa.openoffice.org/issues/show_bug.cgi?id=81482, any comments are welcome.
Have an official openoffice for linux/mips might be a good thing.
Signature · 14 lines
------------------------------------------------ 张福新 江苏中科龙梦科技有限公司 地址：江苏省常熟市虞山镇梦兰工业园 General Manager JiangSu Lemote Corp. Ltd. MengLan, Yushan, Changshu, JiangSu Province, China ZIP: 215500 Tel: 86-512-52308679 Fax: 86-512-52308688 Email: [email protected] http://www.lemote.com ------------------------------------------------
Quoted 4 lines · Fuxin Zhang
It is available at
http://qa.openoffice.org/issues/show_bug.cgi?id=81482, any comments are welcome.
Have an official openoffice for linux/mips might be a good thing.
Hmm, why would anyone need to have asm snippets in a document processing
suite? And it looks like the bits are ABI-dependent, so at least three variations (if the changes are endianness-safe) would be required to handle all the ABIs that we support.
It smells like OpenOffice is doing something outrageously wrong here...
Maciej
Quoted 12 lines · Maciej W. Rozycki
Quoted 5 lines · Fuxin Zhang
It is available at
http://qa.openoffice.org/issues/show_bug.cgi?id=81482, any comments are welcome.
Have an official openoffice for linux/mips might be a good thing.Hmm, why would anyone need to have asm snippets in a document processing
suite? And it looks like the bits are ABI-dependent, so at least three variations (if the changes are endianness-safe) would be required to handle all the ABIs that we support.
Openoffice wants to be able to interact with plugins written in many languages, instead of writting a module for each possible combination it chooses the so called bridge: every language interact with a common middle language.
Quoted 8 lines
It smells like OpenOffice is doing something outrageously wrong here...
Maciej
Quoted 8 lines · Fuxin Zhang
Maciej W. Rozycki ??????:
Quoted 7 lines · Fuxin Zhang
Quoted 6 lines
It is available at
http://qa.openoffice.org/issues/show_bug.cgi?id=81482, any comments are welcome.
Have an official openoffice for linux/mips might be a good thing.
A quick glance revealed already several bugs. (alignment issues, ULH for laoding signed shorts, etc.)
Quoted 9 lines
Quoted 5 lines
Hmm, why would anyone need to have asm snippets in a document processing
suite? And it looks like the bits are ABI-dependent, so at least three variations (if the changes are endianness-safe) would be required to handle all the ABIs that we support.Openoffice wants to be able to interact with plugins written in many languages, instead of writting a module for each possible combination it chooses the so called bridge: every language interact with a common middle language.
So we have now foreign function interfaces for at least OpenOffice, Mozilla, Clisp and GCC's libffi. libffi recently got support for N32/N64 ABIs, and is the only solution which isn't bound to a specific application (as long as GCC is used).
Using libffi from Openoffice looks like the best long-term approach to me.
Thiemo
Quoted 9 lines
Quoted 8 lines
Quoted 6 lines
Hmm, why would anyone need to have asm snippets in a document processing
suite? And it looks like the bits are ABI-dependent, so at least three variations (if the changes are endianness-safe) would be required to handle all the ABIs that we support.Openoffice wants to be able to interact with plugins written in many languages, instead of writting a module for each possible combination it chooses the so called bridge: every language interact with a common middle language.
Quoted 7 lines
So we have now foreign function interfaces for at least OpenOffice, Mozilla, Clisp and GCC's libffi. libffi recently got support for N32/N64 ABIs, and is the only solution which isn't bound to a specific application (as long as GCC is used).
Using libffi from Openoffice looks like the best long-term approach to me.
Good to know the library:) I am not very familiar with the ABI details so the code is more or less only a hack to get the most part work. Maybe the occasional crashes of our OOo are related to the bugs.
Quoted 7 lines
Thiemo
Quoted 16 lines · Thiemo Seufer
Quoted 8 lines · Fuxin Zhang
Maciej W. Rozycki ??????:
Quoted 7 lines · Fuxin Zhang
Quoted 6 lines
It is available at
http://qa.openoffice.org/issues/show_bug.cgi?id=81482, any comments are welcome.
Have an official openoffice for linux/mips might be a good thing.A quick glance revealed already several bugs. (alignment issues, ULH for laoding signed shorts, etc.)
Quoted 3 lines
Quoted 3 lines
Hmm, why would anyone need to have asm snippets in a document processing
suite? And it looks like the bits are ABI-dependent, so at least three variations (if the changes are endianness-safe) would be required to handle all the ABIs that we support.
Quoted 8 lines
Quoted 1 line
Openoffice wants to be able to interact with plugins written in many languages, instead of writting a module for each possible combination it chooses the so called bridge: every language interact with a common middle language.
So we have now foreign function interfaces for at least OpenOffice, Mozilla, Clisp and GCC's libffi. libffi recently got support for N32/N64 ABIs, and is the only solution which isn't bound to a specific application (as long as GCC is used).
Using libffi from Openoffice looks like the best long-term approach to me.
I assume you mean 'Using libffi in...'. I would tend to agree, but I am a bit biased toward libffi.
FWIW, GCC's libffi gets full n32/n64 support in version 4.3 (which has not been released yet) The libffi part seems quite stable though, so you could start experimenting with it now I suppose...
David Daney
Quoted 6 lines · Maciej W. Rozycki
Hmm, why would anyone need to have asm snippets in a document processing
suite? And it looks like the bits are ABI-dependent, so at least three variations (if the changes are endianness-safe) would be required to handle all the ABIs that we support.It smells like OpenOffice is doing something outrageously wrong here...
Normal madness of a (too!) complex piece of software.
Ralf