> FWIW, we're currently putting together (with a lot of help from Subbu > Sastry) an optimizing compiler for JRuby that can do things like > inline Ruby code, propagate constants and types, eliminate dead > code...all the bits and pieces an optimizing compiler would do, if we > had an optimizing compiler backend we could reuse. The ideal situation > would be that we'd use our optimizing compiler to produce optimized > JRuby IR, and then feed that into the JVM-targeting optimizing > compiler in Janino to produce the best-possible-bytecode for our > best-possible-IR.
Have you all looked at Soot and the related libraries from McGill (http://www.sable.mcgill.ca/soot/)? -- You received this message because you are subscribed to the Google Groups "JVM Languages" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jvm-languages?hl=en.
