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: maximum memory for gcj-compiled executable?


Ranjit Mathew wrote:
libjava/prims.cc/_Jv_SetMaximumHeapSize() and _Jv_SetInitialHeapSize() would
be interesting, but they have to be called before calling _Jv_RunMain(). Are
they connected in one way or another to gcj compilation options?

By the way, is there anything like a "gcj.c" entry point into the compiler?
What is the entry point for the "gcj" executable (the place where
commandline options are parsed)?


You might want to see the output of "jvgenmain" ($GCC\lib\gcc-lib\mingw32\3.3),
which is used by GCJ to generate a "normal" main( ) from the class
that you indicate as the main class via the "--main=Foo" option.

I think Erik asked about the "main" for the compiler itself. Your response is about the "main" for the compiled class.

To answer Eruk's question:  The compiler command line is processed
multiple times.  First it is processed by the gcc "driver" program,
which is builtr using gcc.c and java/jvspec.c.  That then invokes
jc1, where it is processed in toplev.c, but it call various
helper routines.
--
	--Per Bothner
per at bothner dot com   http://per.bothner.com/



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