This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: _Jv_SetMaximumHeapSize

From: Andrew Haley <aph at redhat dot com>
To: Erik Poupaert <erik dot poupaert at freestyler-toolkit dot org>
Cc: java at gcc dot gnu dot org
Date: Sun, 21 Sep 2003 14:00:30 +0100
Subject: Re: _Jv_SetMaximumHeapSize
References: <20030921050408.4dd5c816.erik.poupaert@freestyler-toolkit.org><4C16B442-EC16-11D7-BA2F-003065F97F7C@mckinlay.net.nz><20030921124400.5d45c82e.erik.poupaert@freestyler-toolkit.org><16237.37240.419239.257651@cuddles.cambridge.redhat.com><20030921135810.08e7346b.erik.poupaert@freestyler-toolkit.org><16237.38421.168088.24609@cuddles.cambridge.redhat.com><20030921142417.53b88c05.erik.poupaert@freestyler-toolkit.org>

The arg parsing is much more complex than that -- surely -mx can go
anywhere.  Also, we'd be imposing our idea of what args were
permissible in a Java program,

What's wrong with setting the max heap size in a C++ main() function
and then starting your program with the invocation interface?  That
way you can do anything you want before starting Java.

Andrew.

Follow-Ups:
- Re: _Jv_SetMaximumHeapSize
  - From: Erik Poupaert

References:
- stripping libgcj.so.4
  - From: Erik Poupaert
- Re: stripping libgcj.so.4
  - From: Bryce McKinlay
- _Jv_SetMaximumHeapSize
  - From: Erik Poupaert
- _Jv_SetMaximumHeapSize
  - From: Andrew Haley
- Re: _Jv_SetMaximumHeapSize
  - From: Erik Poupaert
- Re: _Jv_SetMaximumHeapSize
  - From: Andrew Haley
- Re: _Jv_SetMaximumHeapSize
  - From: Erik Poupaert

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]