On 2010.05.26., at 0:26, Rémi Forax wrote: > I you write a runtime compiler that is able to optimize/deopt and reopt > when necessary based on type profiling. > You will get a boost. This is applicable for any dynamic languages.
That's my main takeaway from Rémi's post: JSR-292 enables the implementation of incremental type-specializing optimizing/deoptimizing bytecode compilers for your dynamic language. This is the huge deal in the long run. Rémi's current benchmark are largely irrelevant and I don't think we need to get bogged down in arguing over them. Emphasis is on "incremental" and "deoptimizing" - you can do type-specializing compilers without JSR-292 if you want today. However, the ability to swap a dynamic language interpreter with a type-specialized bytecode with a call site granularity, and the ability to switch back to interpreter at, again, a call site granularity, are things you need JSR-292 for. Attila. -- 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.
