RJIT: Prefer STDERR over $stderr

When $stderr is redirected, you'll have no way to see why RJIT got
broken. This reference must always be the actual stderr.

1 files changed, 4 insertions, 4 deletions

diff --git a/lib/ruby_vm/rjit/compiler.rb b/lib/ruby_vm/rjit/compiler.rb
index 964814460b..e5c3adf0ec 100644
--- a/lib/ruby_vm/rjit/compiler.rb
+++ b/lib/ruby_vm/rjit/compiler.rb
@@ -67,8 +67,8 @@ module RubyVM::RJIT
       compile_block(asm, jit:, pc:)
       iseq.body.jit_entry = @cb.write(asm)
     rescue Exception => e
-      $stderr.puts "#{e.class}: #{e.message}"
-      $stderr.puts e.backtrace
+      STDERR.puts "#{e.class}: #{e.message}"
+      STDERR.puts e.backtrace
       exit 1
     end
 
@@ -110,7 +110,7 @@ module RubyVM::RJIT
 
       return block.start_addr
     rescue Exception => e
-      $stderr.puts e.full_message
+      STDERR.puts e.full_message
       exit 1
     end
 
@@ -165,7 +165,7 @@ module RubyVM::RJIT
 
       return target.address
     rescue Exception => e
-      $stderr.puts e.full_message
+      STDERR.puts e.full_message
       exit 1
     end