Age | Commit message (Collapse) | Author |
|
config.sub replaces arm64 with aarch64.
|
|
|
|
is_incremental_marking() can be changed after checking the
flag without locking, especially on `GC.stress = true`.
|
|
https://github.com/ruby/bigdecimal/commit/a109d0984f
|
|
https://github.com/ruby/bigdecimal/commit/034fd2b25e
|
|
Ractor.yield(obj, move: true) and
Ractor.select(..., yield_value: obj, move: true) tried to yield a
value with move semantices, but if the trial is faild, the obj
should not become a moved object.
To keep this rule, `wait_moving` wait status is introduced.
New yield/take process:
(1) If a ractor tried to yield (move:true), make taking racotr's
wait status `wait_moving` and make a moved object by
`ractor_move(obj)` and wakeup taking ractor.
(2) If a ractor tried to take a message from a ractor waiting fo
yielding (move:true), wakeup the ractor and wait for (1).
Notes:
Merged: https://github.com/ruby/ruby/pull/4105
|
|
alen was number of rs, but it should be actions number
(taking ractors + receiving + yielding).
Notes:
Merged: https://github.com/ruby/ruby/pull/4105
|
|
https://github.com/ruby/irb/commit/fc3e1d9e0c
|
|
This is a continuation of 0130e17a410d60a10e7041ce98748b8de6946971. We
need to always use the read barrier
|
|
iff means if and only if, but readers without that knowledge might
assume this to be a spelling mistake. To me, this seems like
exclusionary language that is unnecessary. Simply using "whether"
when describing return values should suffice.
|
|
Co-authored-by: Marc-André Lafortune <github@marc-andre.ca>
|
|
Some objects can survive the GC before compaction, but get collected in
the second compaction. This means we could have objects reference
T_MOVED during "free" in the second, compacting GC. If that is the
case, we need to invalidate those "moved" addresses. Invalidation is
done via read barrier, so we need to make sure the read barrier is
active even during `GC.compact`.
This also means we don't actually need to do one GC before compaction,
we can just do the compaction and GC in one step.
|
|
|
|
Use ractor_wakeup() for same code.
|
|
https://github.com/ruby/net-http/commit/abc6ea1877
|
|
https://github.com/ruby/erb/commit/3d84ea83bc
|
|
and deprecate ERB::Revision.
`'$Date:: $'` has not been working since Git
migration from SVN. I'm sorry.
Because it has been already broken, I'd like to take this opportunity to
make `ERB.version` compatible with `Gem::Version.new`.
https://github.com/ruby/erb/commit/2b4182eb10
|
|
|
|
https://github.com/ruby/erb/commit/c8aa019c26
|
|
|
|
https://github.com/ruby/erb/commit/5df06b8473
|
|
https://github.com/ruby/erb/commit/c68c9470b0
|
|
because, when Ruby 3.1 is released, Ruby 2.5, the last version with the
old method signature, will have been EOL. Therefore we can safely warn
the old interface from Ruby 3.1.
https://github.com/ruby/erb/commit/c3a753f49f
|
|
https://github.com/ruby/erb/commit/012faba2e5
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/4078
|
|
|
|
|
|
|
|
Co-authored-by: ryannevell (Ryan Nevell) <ryan.nevell@gmail.com>
Notes:
Merged: https://github.com/ruby/ruby/pull/4101
|
|
because it was for TestColorPrinter
https://github.com/ruby/irb/commit/7569206fd4
|
|
https://github.com/ruby/irb/commit/eea9c16804
|
|
https://github.com/ruby/irb/commit/d95e8daab3
|
|
https://github.com/ruby/erb/commit/cb59f11ec8
|
|
|
|
iff means if and only if, but readers without that knowledge might
assume this to be a spelling mistake. To me, this seems like
exclusionary language that is unnecessary. Simply using "if and only if"
instead should suffice.
Notes:
Merged: https://github.com/ruby/ruby/pull/4035
|
|
|
|
http://rubyci.s3.amazonaws.com/solaris11-gcc/ruby-master/log/20210119T070008Z.log.html.gz
is caused by:
/export/home/chkbuild/chkbuild-gcc/tmp/build/20210119T150010Z/ruby/lib/reline/ansi.rb:157:in `winsize': Invalid argument - <STDIN> (Errno::EINVAL)
from /export/home/chkbuild/chkbuild-gcc/tmp/build/20210119T150010Z/ruby/lib/reline/ansi.rb:157:in `get_screen_size'
from /export/home/chkbuild/chkbuild-gcc/tmp/build/20210119T150010Z/ruby/lib/reline.rb:168:in `get_screen_size'
from /export/home/chkbuild/chkbuild-gcc/tmp/build/20210119T150010Z/ruby/lib/forwardable.rb:238:in `get_screen_size'
from /export/home/chkbuild/chkbuild-gcc/tmp/build/20210119T150010Z/ruby/lib/irb/color_printer.rb:7:in `pp'
from -e:1:in `<main>'
https://github.com/ruby/irb/commit/1719514598
|
|
After setting ruby2_keywords for bmethod, the rest of arguments
had been ignored. [Bug #17558]
Notes:
Merged: https://github.com/ruby/ruby/pull/4096
|
|
http://ci.rvm.jp/logfiles/brlog.trunk-random1.20210119-074232
https://github.com/ruby/irb/commit/ea87592d4a
|
|
https://github.com/ruby/irb/commit/8e9e6c4037
|
|
https://github.com/ruby/irb/commit/6663057083
|
|
https://github.com/ruby/irb/commit/9b9300dec2
|
|
vm_cc_invalidated_p() returns false when the cme is *NOT*
invalidated.
Notes:
Merged: https://github.com/ruby/ruby/pull/4091
|
|
|
|
http://rubyci.s3.amazonaws.com/ubuntu2004/ruby-master/log/20210119T033003Z.log.html.gz
```
/home/chkbuild/chkbuild/tmp/build/20210119T033003Z/ruby/test/ruby/test_jit.rb:781:
warning: -e:5: warning: possibly useless use of -@ in void context
```
|
|
http://rubyci.s3.amazonaws.com/ubuntu2004/ruby-master/log/20210119T033003Z.log.html.gz
```
/home/chkbuild/chkbuild/tmp/build/20210119T033003Z/ruby/test/ruby/test_pattern_matching.rb:798:
warning: assigned but unused variable - x
```
|
|
|
|
Peephole optimization doesn't play well with find pattern at
least. The only case when a pattern matching could have
unreachable patterns is when we have lasgn/dasgn node, which
shouldn't happen in real-life.
Fixes https://bugs.ruby-lang.org/issues/17534
|
|
forgotten in https://github.com/ruby/ruby/pull/4018
|
|
|