public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andreas Tobler <toa@pop.agri.ch>
To: Ronald Oussoren <oussoren@cistron.nl>
Cc: Dale Johannesen <dalej@apple.com>,  gcc@gcc.gnu.org
Subject: Re: Libffi problem on darwin (MacOSX)
Date: Mon, 26 May 2003 05:24:00 -0000	[thread overview]
Message-ID: <3ED1A256.5040508@pop.agri.ch> (raw)
In-Reply-To: <6AD0ED77-8EF1-11D7-AD55-0003931CFE24@cistron.nl>

Ronald Oussoren wrote:
> 
> On Saturday, May 17, 2003, at 17:21 Europe/Amsterdam, Andreas Tobler  
> wrote:
> 
>>> I just noticed that this might well be stupidity on my part, I tried  
>>> to write a minimal program that demonstrates the problem and that  
>>> runs without problems. Our real code builds ffi_cifs and 
>>> ffi_closures  at runtime, and maybe that code is bogus.
>>
>>
>> Could be, but if I remember right, I didn't complete the structure  
>> passings. Maybe it works, but if not, then I certainly have to check  
>> again. Well, I'll do that anyway.
> 
> 
> The following hack seems to work for the limited tests that I've done.  
> Note that this is *not* based on any understanding of the PPC calling  
> conventions, and therefore likely incorrect.

Thanks, I'll have a look at. It'll take a while since I will test 
against libgcj which needs a longer time to build.
Do you have a dedicated testcase for?

Andreas

  reply	other threads:[~2003-05-26  5:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-16 20:56 Ronald Oussoren
2003-05-16 21:42 ` Dale Johannesen
2003-05-17  6:03   ` Andreas Tobler
2003-05-17 10:17     ` Ronald Oussoren
2003-05-17 15:39       ` Andreas Tobler
2003-05-25 20:49         ` Ronald Oussoren
2003-05-26  5:24           ` Andreas Tobler [this message]
2003-05-26 10:01             ` Ronald Oussoren

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=3ED1A256.5040508@pop.agri.ch \
    --to=toa@pop.agri.ch \
    --cc=dalej@apple.com \
    --cc=gcc@gcc.gnu.org \
    --cc=oussoren@cistron.nl \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).