From: takashikkbn@...
Date: 2020-03-19T03:38:20+00:00
Subject: [ruby-core:97549] [Ruby master Bug#16139] setinstancevariable on MJIT may not check frozen flag

Issue #16139 has been updated by k0kubun (Takashi Kokubun).


As my previous comment https://bugs.ruby-lang.org/issues/16139#note-1 says:

> Note for backporter:
> test_jit's success_count would be 1 in Ruby 2.6, since 2.7 introduced
> "MJIT recompile" on JIT-ed code cancel.

Changing it to `successes_count: 1` seems fine.

----------------------------------------
Bug #16139: setinstancevariable on MJIT may not check frozen flag
https://bugs.ruby-lang.org/issues/16139#change-84706

* Author: k0kubun (Takashi Kokubun)
* Status: Closed
* Priority: Normal
* Assignee: k0kubun (Takashi Kokubun)
* ruby -v: ruby 2.7.0dev (2019-09-03T12:12:31Z master beaabd2308) [x86_64-linux]
* Backport: 2.5: DONTNEED, 2.6: REQUIRED
----------------------------------------
```
class A
  def a
    @a = 1
  end
end

a = A.new
a.a
a.a
a.a
a.freeze
a.a
```

## without JIT
```
$ ruby --disable-gems a.rb
Traceback (most recent call last):
        1: from a.rb:12:in `<main>'
a.rb:3:in `a': can't modify frozen A: #<A:0x00005601af0b0430 @a=1> (FrozenError)
```

## with JIT
```
$ ruby --disable-gems --jit-min-calls=3 --jit-wait a.rb
```
(no error)



-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>