Re: [fedora-java] Using the natively-built Eclipse compiler

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 2005-03-09 at 11:41 +0000, Andrew Haley wrote:
> Ziga Mahkovec writes:
>  > > Something is wrong here. It looks like your ecj is running interpreted 
>  > > both in the "ecj" and "ecj-native" cases.
>  > 
>  > [...]
>  > 
>  > And strace indicates that eclipse.db is opened.  Is there anything else
>  > I can check?
> 
> time gij -verbose:class ...

Thanks Andrew, I put the steps and log files here:
http://www.bootchart.org/misc/ecj/ecj-native.html

It seems that ecj was actually running native in both cases (with or
without gnu.gcj.precompiled.db.path).  Which, looking at the source code
for com.sun.tools.javac.Main, seems right:

@71
loader = new URLClassLoader(new URL[] {
    new URL("gcjlib://" + Config.ECJLIB_INST_DIR + "/" + libname)});

(libname being "lib-org-eclipse-jdt.so")

Moving lib-org-eclipse-jdt.so out of the way speeds up gij/ecj
considerably.

Shouldn't precompiled libraries be configured in runtime, as opposed to
in Main.java?  And I'm not sure why it's actually faster when running
interpreted.

-- 
Ziga



[Index of Archives]     [Red Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]

  Powered by Linux