public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Per Bothner <per@bothner.com>
To: Bernd Kreimeier <bk@lokigames.com>
Cc: 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: <m2snzzhqxs.fsf@magnus.bothner.com> (raw)
In-Reply-To: <14464.63457.898745.667839@ares.lokigames-lan.com>

Bernd Kreimeier <bk@lokigames.com> writes:

> How does this address compilation of Java+JNI source
> to native code? With or w/o the flexibility of TowerJ?

Separate issue, as I expained in a subsequent message.
We handle "compilation of Java+JNI source to native code"
using any C compiler combined JNI run-time support.

The current discussion is purely about how to write the
Classpath libraries, and any other application that
want to *optimize* for JVMs that use CNI, but still
JVMs that only support JNI.  (The former may support
CNI *as well* as JNI;  at gcj will soon support both.)

> If classpath and/or gcj requires CNI, and does not digest
> JNI source as is, then it is not the right tool for many
> purposes (like mine).

Gcj will (soon) digest JNI source as is.  I don't know about
other projects using Classpath.

> Is the combined classpath+gcj roadmap acknowledging that 
> people do use, and will continue to use, JNI? Maybe I am
> missing something - I'd appreciate a cnfirmation. I can't
> make myself dependend on CNI/gcj, and I suspect I am not
> alone.

You will be free to use JNI.  It's your choice: JNI gives you
portability, but it is much slower and much more tedious to use than
CNI.  The current discussion is about a *third* option: Write your
application in CNI (mostly, perhaps with some conditional
compilation), and then use a special compiler (G++) that translates
your CNI source into a JNI binary.  That binary will work with *any*
JVM that support JNI.  That gives you the convenience of writing CNI,
and the speed of CNI when running on a CNI-supported platform.  You
also get (most of) the advantage of JNI portability, since you can use
any JVM that supports JNI, but you are restricted to compiling your
native code using G++.

The goal is to give people (and library writers) options.
-- 
	--Per Bothner
per@bothner.com   http://www.bothner.com/~per/

  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 [this message]
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     ` Jon Olson
2000-04-01  0:00     ` Stuart Ballard
2000-04-01  0:00     ` Per Bothner
  -- 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 Boehm, Hans
2000-04-01  0:00 David Pettersson
2000-04-01  0:00 ` Per Bothner

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=m2snzzhqxs.fsf@magnus.bothner.com \
    --to=per@bothner.com \
    --cc=bk@lokigames.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).