This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Re: libffi: new typedef for return value
- From: Tom Tromey <tromey at redhat dot com>
- To: Jeff Sturm <jsturm at one-point dot com>
- Cc: java-patches at gcc dot gnu dot org, green at redhat dot com
- Date: 22 Feb 2002 16:32:07 -0700
- Subject: Re: libffi: new typedef for return value
- References: <Pine.LNX.4.10.10202181504110.1179-100000@mars.deadcafe.org>
- Reply-to: tromey at redhat dot com
>>>>> "Jeff" == Jeff Sturm <jsturm@one-point.com> writes:
Jeff> Back in _Jv_CallAnyMethodA, I think we can get by allocating a
Jeff> union of
Jeff> union {
Jeff> float f;
Jeff> double d;
Jeff> long long l;
Jeff> ffi_arg a;
Jeff> }
This seems reasonable.
Jeff> but I can't see how we can avoid a switch statement for each
Jeff> possible return type. At least we can avoid specific target
Jeff> macros as in ffitest.c.
This problem is why I had thought about having ffi tell us the
promoted type. The idea is then the ABI difficulties are isolated in
libffi. If there is a weird platform, it won't affect libgcj, which
can simply switch based on the promoted type.
Anthony told me today he'd have some hacking time this weekend, so
hopefully this issue will get resolved soon. This is one of the two
"must fix" bugs I have listed for 3.1.
Tom