From: Sascha H. <sa...@gm...> - 2010-08-31 17:44:23
|
I am actually working on such an optimized call graph dependency optimizer, which should shrink down the whole compilation size. In addition we will remove the need to compile classes that don't need to be compiled. E.g. all the JDK classes need to be compiled once and we can provide it to our users. These two measures should speed up compilation time a lot. // Sascha On Aug 31, 2010 7:08 PM, "Panayotis Katsaloulis" <pan...@pa...> wrote: > > On 31 Αυγ 2010, at 7:18 μ.μ., Sascha Haeberling wrote: > >> Panayotis, >> >> just to understand your proposal: Are you talking about trying to reduce the amount of code we need to translate based on a call graph analysis? Thus throwing out methods that are never called in an application and classes that are never referenced? >> >> // Sascha > > Yes, exactly. > There are already some projects, which do that. Having only class-based dependency is rather expensive, so unfortunately projects like ProGuard is of minimum help. > > I don't know why yGuard which does method-based analysis didn't work, but 1) we can investigate it, 2) bug report it 3) try another library :) > I suspect it had to do with some Scala optimizations; probably with pure Java code we won't have this problem. Still I believe that a more generic solution (i.e. one that also supports other JVM-based languages, like Scala) should be considered. > ------------------------------------------------------------------------------ > This SF.net Dev2Dev email is sponsored by: > > Show off your parallel programming skills. > Enter the Intel(R) Threading Challenge 2010. > http://p.sf.net/sfu/intel-thread-sfd > _______________________________________________ > xmlvm-users mailing list > xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlvm-users |