1
0
Fork 0
mirror of https://github.com/ruby/ruby.git synced 2022-11-09 12:17:21 -05:00

Update README.md

This commit is contained in:
Maxime Chevalier-Boisvert 2021-09-17 14:43:12 -04:00 committed by Alan Wu
parent 5506f2761f
commit e04c3af522

View file

@ -17,10 +17,12 @@ To simplify development, we currently support only macOS and Linux on x86-64, bu
is part of future plans.
This project is open source and falls under the same license as CRuby.
If you wish to learn more about the approach taken, here are some written resources and conference talks:
- [YJIT: Building a New JIT Compiler Inside CRuby](https://pointersgonewild.com/2021/06/02/yjit-building-a-new-jit-compiler-inside-cruby/) ([MoreVMs 2021 talk](https://www.youtube.com/watch?v=vucLAqv7qpc))
- [Simple and Effective Type Check Removal through Lazy Basic Block Versioning](https://arxiv.org/pdf/1411.0352.pdf) ([ECOOP 2015 talk](https://www.youtube.com/watch?v=S-aHBuoiYE0))
- [Interprocedural Type Specialization of JavaScript Programs Without Type Analysis](https://drops.dagstuhl.de/opus/volltexte/2016/6101/pdf/LIPIcs-ECOOP-2016-7.pdf) ([ECOOP 2016 talk](https://www.youtube.com/watch?v=sRNBY7Ss97A))
If you wish to learn more about the approach taken, here are some conference talks and publications:
- [YJIT talk at RubyKaigi 2021](https://www.youtube.com/watch?v=PBVLf3yfMs8)
- [YJIT talk at MoreVMs 2021](https://www.youtube.com/watch?v=vucLAqv7qpc)
- Blog post: [YJIT: Building a New JIT Compiler Inside CRuby](https://pointersgonewild.com/2021/06/02/yjit-building-a-new-jit-compiler-inside-cruby/)
- ECOOP 2016 paper: [Interprocedural Type Specialization of JavaScript Programs Without Type Analysis](https://drops.dagstuhl.de/opus/volltexte/2016/6101/pdf/LIPIcs-ECOOP-2016-7.pdf) ([talk recording](https://www.youtube.com/watch?v=sRNBY7Ss97A))
- ECOOP 2015 paper: [Simple and Effective Type Check Removal through Lazy Basic Block Versioning](https://arxiv.org/pdf/1411.0352.pdf) ([talk recording](https://www.youtube.com/watch?v=S-aHBuoiYE0))
To cite this repository in your publications, please use this bibtex snippet: