Date: Sun, 23 Sep 2001 05:41:37 +0900 From: Fuyuhiko Maruyama <fuyuhik8@is.titech.ac.jp> To: carlo@vis.ethz.ch (Carlo Dapor) Cc: freebsd-java@freebsd.org Subject: Re: JIT and native threads are mutually exclusive ? Message-ID: <55r8szvtz2.wl@tripper.private> In-Reply-To: <20010922194328.9CD6A275B6@naboo.ethz.ch> References: <20010922194328.9CD6A275B6@naboo.ethz.ch>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, At Sat, 22 Sep 2001 21:43:28 +0200 (CEST), Carlo Dapor wrote: > > Dear Java hackers > > I noticed that running java -version -Djava.compiler=OpenJIT (or =shujit) > with jdk1.3.1, it is correctly reported as green threaded and jitted VM. > > When I launch it with -native, either JITs are not found. > > Is this intentional for the time being ? I think it isn't caused by either JavaVM or JIT compiler but by runtime linker. I'm not sure why runtime linker doesn't perform exactly same thing for both of each thread type (green, native). The problem is because JITs have some symbols in libm.so cannot be resolved only with native thread. If you really need JIT compiler that run on native_threads, you can rebuild JIT compiler to link libm in it. It's easy. For OpenJIT, gmake LDLIBS=-lm # OpenJIT's Makefile will perform something strange that install # target rebuild libOpenJIT.so, so you may also need LDLIBS=-lm when # you do `gmake install' For shujit, gmake LIBS=-lm Resulting JIT compilers can run on both green_threads and native_threads. -- Fuyuhiko MARUYAMA <fuyuhik8@is.titech.ac.jp> Matsuoka laboratory, Department of Mathematical and Computing Sciences, Graduate School of Information Science and Engineering, Tokyo Institute of Technology. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55r8szvtz2.wl>