Difference between revisions of "Anti-Optimizations"
From JVMLangSummit
Jump to navigationJump to search (New page: == Anti-Optimizations == Frederik Ohrstrom, Oracle ; Project: ; Blog: ; Slides: Image:file.pdf === Abstract === = Background = = Current Status = = Future = = Key Issues for...) |
|||
| (2 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
== Anti-Optimizations == | == Anti-Optimizations == | ||
| − | Frederik | + | Frederik Öhrström, Oracle |
; Project: | ; Project: | ||
; Blog: | ; Blog: | ||
| − | ; Slides: [[Image: | + | ; Slides: [[Image:Ohrstrom_AST.pdf]] |
=== Abstract === | === Abstract === | ||
| + | |||
| + | Who should be doing these fancy optimizations anyway? — Fredrik Öhrström | ||
| + | |||
| + | JRuby, Jython, etc., transform a source language to bytecodes for the JVM. What kind of optimizations should they do (or not do) before handing the bytecode to the JVM? I will present a few anti-optimizations on bytecode to demonstrate what the JVM can handle and what it cannot handle. It will be visualized using JRockit with a peep hole into the JRockit optimizer. | ||
= Background = | = Background = | ||
Latest revision as of 16:35, 17 September 2009
Contents
Anti-Optimizations
Frederik Öhrström, Oracle
- Project
- Blog
- Slides
- File:Ohrstrom AST.pdf
Abstract
Who should be doing these fancy optimizations anyway? — Fredrik Öhrström
JRuby, Jython, etc., transform a source language to bytecodes for the JVM. What kind of optimizations should they do (or not do) before handing the bytecode to the JVM? I will present a few anti-optimizations on bytecode to demonstrate what the JVM can handle and what it cannot handle. It will be visualized using JRockit with a peep hole into the JRockit optimizer.
Background
Current Status
Future
Key Issues for Discussion
(please expand cooperatively)
