magaudet

5 ms·

1.
SpiderMonkey Newsletter 3 (Firefox 74-75)(mozilla-spidermonkey.github.io)
6 points by magaudet 7y ago|0 comments
2.
by magaudet 10y ago
Chris is definitely an inspiration to many, myself included.
3.
by magaudet 10y ago
For those curious about background: https://blog.cloudera.com/blog/2013/02/inside-cloudera-impal...
4.
by magaudet 10y ago
While the 'Pitfalls' paper was implemented on top of the Testarossa compiler technology (that underlies the OMR compiler technology), the OMR project has spent a lot of engineering effort to make the technology more modular and ea
5.
by magaudet 10y ago
Thanks so much for posting this! That was exactly what I was curious about!
6.
by magaudet 10y ago
Alas, our connection Eclipse is only a legal one. We are an Eclipse Foundation project, but not directly related to the IDE. So won't have any impact on eclim. Sorry!
7.
by magaudet 10y ago
When you say "native languages" you mean a statically compiled language? It's been done before with the technology underlying the OMR compiler component, however there is some work that would need to be done to support this.
8.
Ruby+OMR JIT Compiler: What’s Next?(developer.ibm.com)
70 points by magaudet 10y ago|37 comments
9.
Lua Vermelha(github.com)
1 points by magaudet 10y ago|0 comments
10.
by magaudet 10y ago
I really enjoy meeting up with the JRuby+Truffle people whenever I can at conferences. Though our approaches are really different, there's definitely a cross-pollination of ideas: I've taken huge amounts of inspiration about what
11.
by magaudet 10y ago
Not as well as I should be able to, for sure. In my mind, I look at Truffle and Graal as a potential way forward to build new high performance JVM languages. OMR I see as a way to build language runtimes in C/C++, and have a producti
12.
by magaudet 10y ago
It's great. I do it every day: Headless ubuntu image that I then use Cygwin's X server to SSH into and run xfce4-terminal. Only disappointment has been my laptop's decreasing stability at the windows level... but I can't
13.
by magaudet 10y ago
Someone out of band poked me to give an eye as to what I see the roadmap is. I'm currently working on getting the JIT working with Ruby trunk ( https://github.com/rubyomr-preview/ruby/tree/ruby_2_4_omr_pr.
14.
by magaudet 10y ago
Thanks! That's definitely the exact hope we have for OMR as well. Similarly, improvements in OMR can be shared among all languages using it; ie, because we build both IBM's Java JDK and Ruby on top of OMR, Ruby can benefit from in
15.
by magaudet 10y ago
I have some performance numbers from my original talk at RubyKaigi [1] [2]. Still a ways to to go, but we've built out a reasonable foundation to start with. [1]: http://www.slideshare.net/MatthewGaudet/experiments
16.
by magaudet 10y ago
Officially, OMR is a meaningless title, like LLVM. Similar to LLVM, it once stood for something, but then we realized that it didn't actually match the project's 'charter' quite as well as we had hoped... but had grown f
17.
by magaudet 10y ago
Whoops! That's actually an editing mistake: The Ruby+OMR preview is actually for Ruby 2.2 right now. You can follow the work in progress on trunk (what will become Ruby 2.4 in December) here: https://github.com/rubyomr-
18.
by magaudet 10y ago
Author here: Feel free to AMA!
19.
by magaudet 10y ago
Hey! thanks for the shout out. I would totally love to see more feedback as well! We haven't turned on the issue tracker on that repo, but the glue has it's issues turned on: https://github.com/rubyomr-preview&#x2F
20.
by magaudet 10y ago
Hey, OMR developer here. Ruby+OMR is developed in three pieces: 1) the language independent core, then 2) The language dependent portions (i.e., the VM, and what we call the 'glue') The language independent core is here: https:&#
21.
by magaudet 11y ago
OMR Team member here: Glad to hear you had a good experience with our tech preview! We really appreciated the feedback you provided, and would definitely be willing to take more.
22.
by magaudet 11y ago
Unfortunately no dates. We're still working on this, but we really want to do it right, so we're taking the time we need. Sorry!
23.
by magaudet 11y ago
(IBMer working on said JIT here) As Chris Seaton points out as well, we're not really open source yet. Working on getting there, but it's going to take time. The important thing now is that we can start talking with the community
24.
by magaudet 11y ago
One of the key parts of this project is that we are using the code in production. Each piece is being used in our shipping releases like Java. Open sourcing will happen. Doing it right is very important to us however, so we don't know
25.
by magaudet 11y ago
(BTW: Count me as a very happy user of Bench9k. It's been a very appreciated tool here. I'm hoping to contribute some of our harness customizations back when I have the time to clean up the commits a little).
26.
by magaudet 11y ago
Our approach allows us to integrate with the existing runtimes, enhancing them, rather than having a new implementation. The PyPy approach is capable of much bigger gains, but we can integrate directly into the existing language community,
27.
by magaudet 11y ago
(And working on the Ruby JIT)