From: Per Bothner <per@bothner.com>
To: java-discuss@sourceware.cygnus.com, classpath@gnu.org
Subject: Re: Proposal for CNI/JNI problems
Date: Sat, 01 Apr 2000 00:00:00 -0000 [thread overview]
Message-ID: <m2embnt6zj.fsf@magnus.bothner.com> (raw)
In-Reply-To: <14460.37463.273837.406646@celan.Informatik.Uni-Oldenburg.DE>
"Jochen Hoenicke" <Jochen.Hoenicke@Informatik.Uni-Oldenburg.DE> writes:
> But when I converted the java.util.zip classes, there were some
> issues that a compiler can't solve:
>
> CNI has the method "elements" to access the elements of an array.
It doesn't have to be an all-or-nothing solution. For something
like Release<Type>ArrayElements, we can require that people put
JNI-specific code in an #ifdef __JNI section. Ideally, we want
to remove the need for that, but it might be good enough to
just *minimize* the need for #ifdef __JNI, at least in the short
term. In other words, in can be an incremental process: Start
out by having G++ munge the header mangling and add __jnienv;
then add support for field access; then method access; then
other features depending on priority.
> Another point is how to put pointers to native structures into a
> classfile. Sun didn't solve it well. If I understand the code in
> japhar's java/util/zip correctly sun used an int field to store the
> pointer and later changed it to long to support 64bit architectures.
> libgcj declares natives fields as "gnu.gcj.RawData", but this is not
> portable to other jvms, where the garbage collector doesn't know that
> this class is special. My solution was to put the structure into a
> java byte array, which imposes a little overhead, but should be
> portable (and you get it freed automatically).
Well, we can still use gnu.gcj.RawData (or gnu.RawData) with JNI.
However, for the JNI case gnu.gcj.RawData would be a real class:
public class RawData
{
int index;
}
Here index is an index into a global RawDataTable
typedef void * RawPointer;
RawPointer** RawDataTable;
#ifdef __JNI
#define JvGetRawData(rdata) RawDataTable[rdata->index]
#define JvAllocRawData(data) new Rawdata(AssignrawdataIndex(data))
#define JvFreeRawData(data) RawDataTable[rdata->index] = NULL
#else
#define JvGetRawData(rdata) ((RawPointer) rdata)
#define JvAllocRawData(data) (data)
#define JvFreeRawData(data) { }
#endif
--
--Per Bothner
per@bothner.com http://www.bothner.com/~per/
next prev parent reply other threads:[~2000-04-01 0:00 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-01 0:00 Paul Fisher
2000-04-01 0:00 ` Per Bothner
2000-04-01 0:00 ` Paul Fisher
2000-04-01 0:00 ` Per Bothner
2000-04-01 0:00 ` Aaron M. Renn
2000-04-01 0:00 ` Stuart Ballard
2000-04-01 0:00 ` Chris Blizzard
2000-04-01 0:00 ` Chris Blizzard
2000-04-01 0:00 ` Bernd Kreimeier
2000-04-01 0:00 ` Per Bothner
2000-04-01 0:00 ` Bernd Kreimeier
2000-04-01 0:00 ` Per Bothner
2000-04-01 0:00 ` Bernd Kreimeier
2000-04-01 0:00 ` Per Bothner
2000-04-01 0:00 ` Bernd Kreimeier
2000-04-01 0:00 ` Per Bothner
2000-04-01 0:00 ` Alexandre Oliva
2000-04-01 0:00 ` Bernd Kreimeier
2000-04-01 0:00 ` Jochen Hoenicke
2000-04-01 0:00 ` Stuart Ballard
2000-04-01 0:00 ` Per Bothner [this message]
2000-04-01 0:00 ` Jon Olson
-- strict thread matches above, loose matches on Subject: below --
2000-04-01 0:00 Lam.Mark
2000-04-01 0:00 ` Aaron M. Renn
2000-04-01 0:00 ` Brian Jones
2000-04-01 0:00 David Pettersson
2000-04-01 0:00 ` Per Bothner
2000-04-01 0:00 Boehm, Hans
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=m2embnt6zj.fsf@magnus.bothner.com \
--to=per@bothner.com \
--cc=classpath@gnu.org \
--cc=java-discuss@sourceware.cygnus.com \
/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).