Libffi problem on darwin (MacOSX)
Ronald Oussoren
oussoren@cistron.nl
Mon May 26 10:01:00 GMT 2003
On Monday, May 26, 2003, at 07:12 Europe/Amsterdam, Andreas Tobler
wrote:
> 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?
I don't have a small standalone testcase for this problem. The problem
is triggered by a unittest in PyObjC, I can use that to check patches.
Ronald
More information about the Gcc
mailing list