All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Daney <ddaney@avtrex.com>
To: Thiemo Seufer <ths@networkno.de>
Cc: Fuxin Zhang <fxzhang@ict.ac.cn>,
	"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 09:20:13 -0700	[thread overview]
Message-ID: <46F9353D.6050107@avtrex.com> (raw)
In-Reply-To: <20070925133812.GB2333@networkno.de>

Thiemo Seufer wrote:
> 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.

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

  parent reply	other threads:[~2007-09-25 16:20 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
2007-09-25 13:55       ` Fuxin Zhang
2007-09-25 16:20       ` David Daney [this message]
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=46F9353D.6050107@avtrex.com \
    --to=ddaney@avtrex.com \
    --cc=debian-mips@lists.debian.org \
    --cc=fxzhang@ict.ac.cn \
    --cc=linux-mips@linux-mips.org \
    --cc=macro@linux-mips.org \
    --cc=ths@networkno.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.