From: Matthew Fortune <Matthew.Fortune@imgtec.com>
To: "java-patches@gcc.gnu.org" <java-patches@gcc.gnu.org>
Cc: "aurelien@aurel32.net" <aurelien@aurel32.net>,
Yunqiang Su <Yunqiang.Su@imgtec.com>
Subject: [RFC] interpreter use of closures and return types
Date: Wed, 22 Jun 2016 11:54:00 -0000 [thread overview]
Message-ID: <6D39441BF12EF246A7ABCE6654B023537E45723C@HHMAIL01.hh.imgtec.org> (raw)
Hi,
While working on getting mips64el support in place for Debian we found a
bug relating to libgcj/libffi and closures for MIPS n32 and n64. The bug
is essentially that return types <= 32bit do not end up correctly sign
extended in registers when a function is called via a closure. A test case
showing what I think the problem boils down to is at the end of this email.
Switch between the two lines in foo_binding to see the difference. Note
that this will not fail on x86 but I believe it will fail on any big endian
architecture.
The root of the problem seems to be in a oddity of FFI that integer return
values less than word (or rather register) size are returned as an ffi_arg.
The java interpreter does not appear to adhere to this and the patch below
seems to fix the issue. Can anyone comment if this looks like the right
approach?
I think there may be a similar issue in the lang/reflect/natVMProxy.cc
code (unbox function) by code inspection alone but haven't investigated
further.
If this looks OK I'll do some full testsuite runs.
Thanks,
Matthew
libjava/
* interpret-run.cc: Return integers as ffi_arg instead of jint.
diff --git a/libjava/interpret-run.cc b/libjava/interpret-run.cc
index a4c2d4d..6be354e 100644
--- a/libjava/interpret-run.cc
+++ b/libjava/interpret-run.cc
@@ -1838,7 +1838,7 @@ details. */
return;
insn_ireturn:
- *(jint *) retp = POPI ();
+ *(ffi_arg *) retp = POPI ();
return;
insn_return:
Here is the test case to show the effect of getting int vs ffi_arg wrong on
n32/n64. It will say that the result is negative only when using ffi_arg as
the return type.
#include <stdio.h>
#include <ffi.h>
__attribute__((noinline))
int foo(void)
{
return -1;
}
/* Acts like puts with the file given at time of enclosure. */
void foo_binding(ffi_cif *cif, void *ret, void* args[], void* none)
{
*(int *)ret = foo();
// *(ffi_arg *)ret = foo();
}
typedef int (*foo_t)();
int main()
{
ffi_cif cif;
ffi_closure *closure;
void *bound_foo;
int rc;
closure = ffi_closure_alloc(sizeof(ffi_closure), &bound_foo);
if (closure)
{
/* Initialize the cif */
if (ffi_prep_cif(&cif, FFI_DEFAULT_ABI, 0,
&ffi_type_sint32, NULL) == FFI_OK)
{
if (ffi_prep_closure_loc(closure, &cif, foo_binding,
NULL, bound_foo) == FFI_OK)
{
rc = ((foo_t)bound_foo)();
fprintf(stderr, "is result negative: %s\n", (rc < 0)? "yes":"no");
}
}
}
ffi_closure_free(closure);
return 0;
}
next reply other threads:[~2016-06-22 11:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 11:54 Matthew Fortune [this message]
2016-06-22 12:28 ` Anthony Green
2016-06-22 12:53 ` Matthew Fortune
2016-06-22 16:49 ` Aurelien Jarno
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=6D39441BF12EF246A7ABCE6654B023537E45723C@HHMAIL01.hh.imgtec.org \
--to=matthew.fortune@imgtec.com \
--cc=Yunqiang.Su@imgtec.com \
--cc=aurelien@aurel32.net \
--cc=java-patches@gcc.gnu.org \
/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).