Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Destaque
Destaque (7)
Semelhante a Eclipse OMR: a modern toolkit for building language runtimes
Semelhante a Eclipse OMR: a modern toolkit for building language runtimes (20)
Mais de Mark Stoodley
Mais de Mark Stoodley (7)
Último
Último (20)
Eclipse OMR: a modern toolkit for building language runtimes
- 1. Eclipse OMR A Modern Toolkit for Building Language Run:mes Mark Stoodley OMR Project Technical Lead
- 2. About me • Mark Stoodley mstoodle@ca.ibm.com @mstoodle • Senior software developer in Toronto, Canada working for IBM Runtime Technologies • Spent the last 14 years building JIT compilers in JVMs • OMR Project Technical Lead 2
- 5. OMR is… 5
- 10. Java Execution Environment What’s in a Language Run:me for Java? Java Plaaorm Abstrac:on Layer Java Garbage Collector Java Diagnos:c Services Source Code Bytecode/AST Compiler 10 Java Just-In-Time Compiler Interpreter Java Source Java Bytecode Compiler Java Bytecode Interpreter
- 11. Ruby Execution Environment What’s in a Language Run:me for Ruby? Ruby Plaaorm Abstrac:on Layer Ruby Garbage Collector Ruby Diagnos:c Services Source Code Bytecode/AST Compiler 11 Ruby Just-In-Time Compiler Interpreter Ruby Source Ruby Bytecode Compiler Ruby Bytecode Interpreter
- 12. Python Execution Environment What’s in a Language Run:me for Python? Python Plaaorm Abstrac:on Layer Python Garbage Collector Python Diagnos:c Services Source Code Bytecode/AST Compiler 12 Python Just-In-Time Compiler Interpreter Python Source Python Bytecode Compiler Python Bytecode Interpreter
- 13. • Investment in one runtime has no leverage in other runtimes • Cloud => many languages => expensive to advance platform But all language runtimes are completely different implementations 13
- 14. Java Execution Environment OMR started from IBM J9 Java… J9 Java Plaaorm Abstrac:on Layer J9 Java Garbage Collector J9 Java Diagnos:c Services Source Code Bytecode/AST Compiler 14 J9 Java Just-In-Time Compiler Interpreter Java Source J9 Java Bytecode Compiler J9 Java Bytecode Interpreter
- 15. J9 Java JIT Compiler Glue J9 Java Execution Environment By concentra:ng “Java”ness into a “glue” layer for each core component OMR Plaaorm Abstrac:on Layer OMR Garbage Collector OMR Diagnos:c Services Source Code Bytecode/AST Compiler 15 Interpreter Java Source J9 Java Bytecode Compiler J9 Java Bytecode Interpreter J9 Java Diagnos:c Glue J9 Java GC Glue OMR Just in Time (JIT) Compiler
- 16. 1. OMR has no language seman:cs 2. OMR is not a language run:me 3. OMR can become part of any language run:me 16
- 19. Ingredients Now Available! port plaaorm abstrac:on (por:ng) library thread cross plaaorm pthread-like threading library gc garbage collec:on framework for managed heaps vm APIs to manage per-interpreter and per-thread contexts omrtrace tracing library for communica:on with IBM Health Center monitoring tools omrsigcompat signal handling compa:bility library example demonstra:on code to show how a language run:me might consume some OMR components, also used for tes:ng fvtest a language independent test framework so that OMR components can be tested outside of a language run:me + a few others …a liBle less than 200KLOC at this point 19
- 20. More ingredients coming soon! diag: more diagnos:c support for run:mes to aid run:me developers and users hcagentcore: core IBM Health Center agent code to connect with a run:me gc: adding genera:onal and other policies / technologies jit: Just In Time compiler and na:ve code genera:on tools docs: <gasp> we need more overview documenta:on tests: more tests to ensure high quality contribu:ons 20
- 22. Mock it up! • fvtest directory – Leverages Google test unit test framework – Component tests for: • Port, gc, signals, threads, vm fork, trace, agents • U:li:es and data structures, method dic:onary • etc. • “make test” forms the basis for high quality contribu:ons – Contribu:ons cannot cause new failures in “make test” 22
- 25. Ruby + OMR Technology Preview • We ported OMR into CRuby – Focus on easy integra:on and compa:bility – All C extensions work as-is – It runs Rails! • Presented at Ruby Kaigi 2015, FOSDEM & jFokus 2016 • Available on github: – Download docker images for 64-bit X86, OpenPOWER, and LinuxONE @ hBps://goo.gl/P3yXuy 25
- 27. Health Center • Provides a live view of run:me details • Works with IBM JDK, IBM Node.js, and Ruby+OMR Technology Preview • hBp://goo.gl/u3VITI 27
- 28. Health Center – CRuby Method Profiling 28
- 29. Health Center – OMR GC Statistics from CRuby 29
- 30. Garbage Collec:on and Memory Visualizer 30 • Provides a graphical details on GC events post mortem from verbose:gc logs • Works with IBM JDK, IBM Node.js and Ruby+OMR Technology Preview • hBps://goo.gl/YwNrmI
- 34. 28.4 17.2 5.5 1.1 0 5 10 15 20 25 30 Ruby 2.2.2 Ruby 2.2.2 + OMR Ruby 2.2.2 + OMR + JIT OMR Il Builder Pow(2,N) 34 Time (seconds)
- 35. • We know it works; we tried it! • IBM Java SDK will con:nue to consume OMR technology and work directly in open OMR project • Project is open to all; we welcome others – New contributors! – New plaaorms! – New languages! – New tool interfaces! – New technology to help build run:mes! 35
- 36. Wrap Up • Eclipse OMR: high quality language run:me components 1. has no language seman:cs 2. is not a language run:me 3. can become part of any language run:me • We are live at Eclipse as an incubator! – hBp://www.eclipse.org/omr – hBps://github.com/eclipse/omr – omr-dev@eclipse.org – Contact us via mailing list or GItHub issues • Dual Eclipse 1.0 + Apache 2.0 license • We would love to see you all there! 36
- 37. • Almost no one starts a new project saying: – First, I’ll write the firmware from scratch … – First, I’ll write the file system from scratch … – First, I’ll write the display drivers from scratch … • We would like to make these statements just as unlikely: – First, I’ll write the cross platform port library from scratch … – First, I’ll write a garbage collector technology from scratch … – First, I’ll write the JIT compiler technology from scratch … 37 A Par:ng Thought
- 38. • Almost no one starts a new project saying: – First, I’ll write the firmware from scratch … – First, I’ll write the file system from scratch … – First, I’ll write the display drivers from scratch … • We would like to make these statements just as unlikely: – First, I’ll write the cross platform port library from scratch … – First, I’ll write the garbage collector from scratch … – First, I’ll write the JIT compiler from scratch … 38 A Par:ng Thought
- 40. Learn more about OMR! • A VM is a VM is a VM: The Secret Path to High Performance Mul: Language Run:mes (Mark Stoodley, JVM Languages Summit 2015) hBps://www.youtube.com/watch?v=kOnyJurioyw • Beyond the Coffee Cup: Leveraging Java Run:me Technologies for the Polyglot (Daryl Maier, Java One 2015) hBp://www.slideshare.net/0xdaryl/javaone-2015-con7547-beyond-the-coffee-cup-leveraging-java-run:me-technologies-for-polyglot • What’s in an Object? Java Garbage Collec:on for the Polyglot (Charlie Gracie, Java One 2015) hBp://www.slideshare.net/charliegracie1/javaone-whats-in-an-object • Building Your Own Language Run:me (Angela Lin, Robert Young, Craig Lehmann, Xiaoli Liang, CASCON 2015) hBps://ibm.box.com/s/7xdg25we2ezmdjjbqdys30d7dl1iyo49 • It’s Dangerous to GC alone. Take this! (Robert Young and Craig Lehmann, Ruby Kaigi 2015) hBp://www.slideshare.net/craiglehmann/the-omr-gc-talk-ruby-kaigi-2015 • Experiments in sharing Java VM Technology with CRuby (MaBhew Gaudet, Ruby Kaigi 2015) hBp://www.slideshare.net/MaBhewGaudet/experiments-in-sharing-java-vm-technology-with-cruby • Ruby and OMR: Experiments in u:lizing OMR technologies in Ruby (MRI) (Charlie Gracie, FOSDEM 2016) hBp://www.slideshare.net/CharlieGracie/ruby-and-omr • A JVMs Journey into Polyglot Run:mes (Charlie Gracie, jFokus 2016) hBps://t.co/efCKf6aCB4 • OMR: A modern toolkit for building language run:mes (Mark Stoodley, EclipseCon March 2016) [ You’re reading it right now! ] • Ruby+OMR Technology Preview github project with docker images for Linux on LinuxONE, OpenPOWER, and X86 hBps://github.com/rubyomr-preview/rubyomr-preview • Contact: – Mark Stoodley (mstoodle@ca.ibm.com, @mstoodle) OMR Project Technical Lead 40
- 41. Trademarks, Copyrights, Disclaimers IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion. IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of other IBM trademarks is available on the web at "Copyright and trademark information" at http://www.ibm.com/legal/copytrade.shtml Other company, product, or service names may be trademarks or service marks of others. THE INFORMATION CONTAINED IN THIS PRESENTATION IS PROVIDED FOR INFORMATIONAL PURPOSES ONLY. WHILE EFFORTS WERE MADE TO VERIFY THE COMPLETENESS AND ACCURACY OF THE INFORMATION CONTAINED IN THIS PRESENTATION, IT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. IN ADDITION, THIS INFORMATION IS BASED ON IBM’S CURRENT PRODUCT PLANS AND STRATEGY, WHICH ARE SUBJECT TO CHANGE BY IBM WITHOUT NOTICE. IBM SHALL NOT BE RESPONSIBLE FOR ANY DAMAGES ARISING OUT OF THE USE OF, OR OTHERWISE RELATED TO, THIS PRESENTATION OR ANY OTHER DOCUMENTATION. NOTHING CONTAINED IN THIS PRESENTATION IS INTENDED TO, NOR SHALL HAVE THE EFFECT OF, CREATING ANY WARRANTIES OR REPRESENTATIONS FROM IBM (OR ITS SUPPLIERS OR LICENSORS), OR ALTERING THE TERMS AND CONDITIONS OF ANY AGREEMENT OR LICENSE GOVERNING THE USE OF IBM PRODUCTS OR SOFTWARE. © Copyright International Business Machines Corporation 2016. All rights reserved. 41
- 42. Addi:onal Important Disclaimers • THE INFORMATION CONTAINED IN THIS PRESENTATION IS PROVIDED FOR INFORMATIONAL PURPOSES ONLY. • WHILST EFFORTS WERE MADE TO VERIFY THE COMPLETENESS AND ACCURACY OF THE INFORMATION CONTAINED IN THIS PRESENTATION, IT IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. • ALL PERFORMANCE DATA INCLUDED IN THIS PRESENTATION HAVE BEEN GATHERED IN A CONTROLLED ENVIRONMENT. YOUR OWN TEST RESULTS MAY VARY BASED ON HARDWARE, SOFTWARE OR INFRASTRUCTURE DIFFERENCES. • ALL DATA INCLUDED IN THIS PRESENTATION ARE MEANT TO BE USED ONLY AS A GUIDE. • IN ADDITION, THE INFORMATION CONTAINED IN THIS PRESENTATION IS BASED ON IBM’S CURRENT PRODUCT PLANS AND STRATEGY, WHICH ARE SUBJECT TO CHANGE BY IBM, WITHOUT NOTICE. • IBM AND ITS AFFILIATED COMPANIES SHALL NOT BE RESPONSIBLE FOR ANY DAMAGES ARISING OUT OF THE USE OF, OR OTHERWISE RELATED TO, THIS PRESENTATION OR ANY OTHER DOCUMENTATION. • NOTHING CONTAINED IN THIS PRESENTATION IS INTENDED TO, OR SHALL HAVE THE EFFECT OF: • - CREATING ANY WARRANT OR REPRESENTATION FROM IBM, ITS AFFILIATED COMPANIES OR ITS OR THEIR SUPPLIERS AND/OR LICENSORS 42