From: Bryce McKinlay <bryce@waitaki.otago.ac.nz>
To: Nic Ferrier <nferrier@tapsellferrier.co.uk>
Cc: tromey@redhat.com, Andrew Pinski <pinskia@physics.uc.edu>,
GCC-Java <java@gcc.gnu.org>
Subject: Re: gij and -cp/-classpath
Date: Tue, 09 Apr 2002 18:19:00 -0000 [thread overview]
Message-ID: <3CB3913A.1090807@waitaki.otago.ac.nz> (raw)
In-Reply-To: <87adscv06q.fsf@pooh-sticks-bridge.tapsellferrier.co.uk>
Nic Ferrier wrote:
>Bryce McKinlay <bryce@waitaki.otago.ac.nz> writes:
>
>>Yes, the idea is to have one argument parser which can be shared by:
>>
>>- gij command line
>>- vm_args for CNI & JNI invocation API
>>- an environment variable (LIBGCJ_ARGS or some such) which sets VM
>>parameters for any gcj binary
>>
>
>I don't understand that last part: don't *all* gcj applications have
>to use the invocation API? I presumed that GCJ compiled (native) code
>was wrapped with some invocation caller.
>
Yep, but parameters specified on the command line to a native gcj binary
go directly to the Java main() method, not vm_args. So if we want to be
able to specify VM/runtime arguments as well (eg max heap size,
classpath, debugging flags, etc), it needs to be done in an environment
variable. It should be just a matter of having something to read the
LIBGCJ_ARGS and pass it to _Jv_CreateJavaVM().
regards
Bryce.
prev parent reply other threads:[~2002-04-10 1:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-09 12:55 Andrew Pinski
2002-04-09 12:59 ` Tom Tromey
2002-04-09 17:32 ` Nic Ferrier
2002-04-09 18:00 ` Bryce McKinlay
2002-04-09 18:05 ` Nic Ferrier
2002-04-09 18:19 ` Bryce McKinlay [this message]
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=3CB3913A.1090807@waitaki.otago.ac.nz \
--to=bryce@waitaki.otago.ac.nz \
--cc=java@gcc.gnu.org \
--cc=nferrier@tapsellferrier.co.uk \
--cc=pinskia@physics.uc.edu \
--cc=tromey@redhat.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).