Your message dated Sun, 16 Mar 2003 18:02:34 +0100
with message-id [EMAIL PROTECTED]
and subject line libgcj/9078: libffi: problems with uint8 on powerpc
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt
Hi there,
The problem was effectively due to my misreading of libffi's
documentation for return values (which are handled differently from
parameters). Thanks for your help identifying the problem.
You should probably close the bug.
Thanks,
Etienne
(upstream SableVM author)
--
Etienne M.
On Sat, 28 Dec 2002, Matthias Klose wrote:
ffi_type_uint8 and other arguments shorter than one word are
not passed in correctly to the function called by ffi_call.
For an ffi_type_uint8, ffi_call expects the corresponding value
pointer to be a (unsigned char *). So this is correct usage:
Synopsis: libffi: problems with uint8 on powerpc
Responsible-Changed-From-To: unassigned-jsturm
Responsible-Changed-By: jsturm
Responsible-Changed-When: Sun Dec 29 08:13:07 2002
Responsible-Changed-Why:
I'll handle it.
State-Changed-From-To: open-feedback
State-Changed-By: jsturm
Thank you very much for your problem report.
It has the internal identification `libgcj/9078'.
The individual assigned to look at your
report is: unassigned.
Category: libgcj
Responsible:unassigned
Synopsis: libffi: problems with uint8 on powerpc
Arrival-Date: Sat Dec 28
5 matches
Mail list logo
