From: Thiemo Seufer <ths@networkno.de>
To: Fuxin Zhang <fxzhang@ict.ac.cn>
Cc: "Maciej W. Rozycki" <macro@linux-mips.org>,
Fuxin Zhang <zhangfx@lemote.com>,
debian-mips@lists.debian.org, linux-mips@linux-mips.org
Subject: Re: About openoffice linux/mips porting
Date: Tue, 25 Sep 2007 14:38:12 +0100 [thread overview]
Message-ID: <20070925133812.GB2333@networkno.de> (raw)
In-Reply-To: <46F90841.1040903@ict.ac.cn>
Fuxin Zhang wrote:
> Maciej W. Rozycki ??????:
>> On Tue, 25 Sep 2007, Fuxin Zhang wrote:
>>
>>
>>> 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.)
>> 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
next prev parent reply other threads:[~2007-09-25 13:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 12:43 About openoffice linux/mips porting Fuxin Zhang
2007-09-25 13:10 ` Maciej W. Rozycki
2007-09-25 13:08 ` Fuxin Zhang
2007-09-25 13:38 ` Thiemo Seufer [this message]
2007-09-25 13:55 ` Fuxin Zhang
2007-09-25 16:20 ` David Daney
2007-09-25 13:36 ` Ralf Baechle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070925133812.GB2333@networkno.de \
--to=ths@networkno.de \
--cc=debian-mips@lists.debian.org \
--cc=fxzhang@ict.ac.cn \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=zhangfx@lemote.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox