Ruby 2.6.0-preview2 released with JIT

#1

Post by 15DCFA8F » Sun, Jun 03, 2018, 4:22 PM UTC

Ruby 2.6.0-preview2 released with JIT
ruby-lang.org

Re: Ruby 2.6.0-preview2 released with JIT

#2

Post by alberth » Sun, Jun 03, 2018, 5:18 PM UTC

What’s the current sentiment as for what will ultimately lead to the best performance of executing Ruby?

From my uneducated perspective, seems like Graal VM could become the de facto Ruby deployment stack.

https://github.com/oracle/truffleruby

Re: Ruby 2.6.0-preview2 released with JIT

#3

Post by karag » Sun, Jun 03, 2018, 5:38 PM UTC

why ruby innovate and not python ?

Re: Ruby 2.6.0-preview2 released with JIT

#4

Post by blattimwind » Sun, Jun 03, 2018, 5:41 PM UTC

> Unlike ordinary JIT compilers for other languages, Ruby’s JIT compiler does JIT compilation in a unique way, which prints C code to a disk and spawns common C compiler process to generate native cod e.

Oh dear god.

Re: Ruby 2.6.0-preview2 released with JIT

#5

Post by wwarner » Sun, Jun 03, 2018, 5:41 PM UTC

A standardized AST! That's a big win.

Re: Ruby 2.6.0-preview2 released with JIT

#6

Post by pavanky » Sun, Jun 03, 2018, 5:45 PM UTC

blattimwind wrote: post #4

> Unlike ordinary JIT compilers for other languages, Ruby’s JIT compiler does JIT compilation in a unique way, which prints C code to a disk and spawns common C compiler process to generate native cod e. Oh dear god.

Why aren't they using LLVM :-/

Re: Ruby 2.6.0-preview2 released with JIT

#7

Post by my123 » Sun, Jun 03, 2018, 5:45 PM UTC

blattimwind wrote: post #4

> Unlike ordinary JIT compilers for other languages, Ruby’s JIT compiler does JIT compilation in a unique way, which prints C code to a disk and spawns common C compiler process to generate native cod e. Oh dear god.

Same as the last stage of the SQL Server query optimizer then. (hey MS)

Re: Ruby 2.6.0-preview2 released with JIT

#8

Post by bastawhiz » Sun, Jun 03, 2018, 5:48 PM UTC

pavanky wrote: post #6

blattimwind wrote: post #4

> Unlike ordinary JIT compilers for other languages, Ruby’s JIT compiler does JIT compilation in a unique way, which prints C code to a disk and spawns common C compiler process to generate native cod e. Oh dear god.

Why aren't they using LLVM :-/

They answer this on the github:

> Unstable interfaces. An LLVM JIT is already used by Rubicon. A lot of efforts in preparation of code used by RTL insns (an environment)

https://github.com/vnmakarov/ruby/tree/rtl_mjit_branch#a-few...

Re: Ruby 2.6.0-preview2 released with JIT

#9

Post by _ZeD_ » Sun, Jun 03, 2018, 5:49 PM UTC

karag wrote: post #3

why ruby innovate and not python ?

why not both? and btw, you may look at pypy if you like this kind of innovations

Re: Ruby 2.6.0-preview2 released with JIT

#10

Post by jashmatthews » Sun, Jun 03, 2018, 5:51 PM UTC

pavanky wrote: post #6

blattimwind wrote: post #4

> Unlike ordinary JIT compilers for other languages, Ruby’s JIT compiler does JIT compilation in a unique way, which prints C code to a disk and spawns common C compiler process to generate native cod e. Oh dear god.

Why aren't they using LLVM :-/

The new Ruby method JIT can use either GCC or clang as the backend. It uses C as an intermediate representation.