Age | Commit message (Collapse) | Author |
|
https://github.com/ruby/logger/commit/5f70168ac5
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/2733
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/2733
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/2733
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/2733
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/2733
|
|
(This is the second try of 036bc1da6c6c9b0fa9b7f5968d897a9554dd770e.)
If iseq is GC'ed, the pointer of iseq may be reused, which may hide a
deprecation warning of keyword argument change.
http://ci.rvm.jp/results/trunk-test1@phosphorus-docker/2474221
```
1) Failure:
TestKeywordArguments#test_explicit_super_kwsplat [/tmp/ruby/v2/src/trunk-test1/test/ruby/test_keyword.rb:549]:
--- expected
+++ actual
@@ -1 +1 @@
-/The keyword argument is passed as the last hash parameter.* for `m'/m
+""
```
This change ad-hocly adds iseq_unique_id for each iseq, and use it
instead of iseq pointer. This covers the case where caller is GC'ed.
Still, the case where callee is GC'ed, is not covered.
But anyway, it is very rare that iseq is GC'ed. Even when it occurs, it
just hides some warnings. It's no big deal.
|
|
|
|
|
|
This reverts commit 036bc1da6c6c9b0fa9b7f5968d897a9554dd770e.
This caused a failure on iseq_binary mode.
http://ci.rvm.jp/results/trunk-iseq_binary@silicon-docker/2474587
Numbering iseqs is not trivial due to dump/load.
|
|
This reverts commit 751a9b32e5a53336768eb878de1827245a3292bf.
|
|
|
|
The function assumed that the LSB of `callee` was 0.
|
|
If iseq is GC'ed, the pointer of iseq may be reused, which may hide a
deprecation warning of keyword argument change.
http://ci.rvm.jp/results/trunk-test1@phosphorus-docker/2474221
```
1) Failure:
TestKeywordArguments#test_explicit_super_kwsplat [/tmp/ruby/v2/src/trunk-test1/test/ruby/test_keyword.rb:549]:
--- expected
+++ actual
@@ -1 +1 @@
-/The keyword argument is passed as the last hash parameter.* for `m'/m
+""
```
This change ad-hocly adds iseq_unique_id for each iseq, and use it
instead of iseq pointer. This covers the case where caller is GC'ed.
Still, the case where callee is GC'ed, is not covered.
But anyway, it is very rare that iseq is GC'ed. Even when it occurs, it
just hides some warnings. It's no big deal.
|
|
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/2731
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/2731
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/2731
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/2731
|
|
|
|
|
|
|
|
|
|
|
|
https://github.com/ruby/irb/commit/da6577a88c
|
|
https://github.com/ruby/irb/commit/4be3158358
|
|
String#grapheme_clusters"
This reverts commit 2b0b19b87c60d2cdb329979acbb96e12a1f940e7.
New IRB parser needs new Ripper what has lex_state too. The new Ripper is
adopted by Ruby 2.5 or later.
https://github.com/ruby/irb/commit/9ab6e35a2c
|
|
https://github.com/ruby/irb/commit/2b0b19b87c
|
|
https://github.com/ruby/reline/commit/33e8c8f15b
|
|
```
1) Error:
TestFileExhaustive#test_socket_p:
ArgumentError: too long unix socket path (109bytes given but 108bytes max)
/export/home/users/chkbuild/cb-sunc/tmp/build/20191207T024036Z/ruby/test/ruby/test_file_exhaustive.rb:155:in `initialize'
```
|
|
|
|
|
|
When interfaces do not include localhost,
some other tests may fail.
|
|
This commit introduces an "inline ivar cache" struct. The reason we
need this is so compaction can differentiate from an ivar cache and a
regular inline cache. Regular inline caches contain references to
`VALUE` and ivar caches just contain references to the ivar index. With
this new struct we can easily update references for inline caches (but
not inline var caches as they just contain an int)
|
|
|
|
|
|
|
|
MJIT_CC is always an absolute path.
|
|
|
|
instead of ruby/config.h, per samuel's request.
https://github.com/ruby/ruby/commit/dbfd4b780e3914a3f27e92c2248254452bf0fd6b#diff-7fd78c3cc8a19b7e0637502983ec26ff
|
|
This reverts commit 0d7d8b2989e1738dd902d354cc41186899e6b71e,
but restore `$warnflags` without the flag, to get rid of using
deprecated functions.
|
|
```
.../gems/did_you_mean-1.3.1/lib/did_you_mean/version.rb:2: warning: already initialized constant DidYouMean::VERSION
.../lib/did_you_mean/version.rb:2: warning: previous definition of VERSION was here
```
|
|
|
|
|
|
|
|
`args_ptr` can be corrupted by interrupt handlers.
Pointed by nagachika <https://ruby-trunk-changes.hatenablog.com/entry/ruby_trunk_changes_20191204>.
|
|
I'm not entirely sure why, but test_set_winsize_console gets stuck on
Solaris (and if I recall, macOS). I found a hack for FreeBSD, so I want
to give it a try on Solaris too.
|
|
https://travis-ci.org/ruby/ruby/jobs/620972117
|
|
0b19e15a1239bff9ae854f522f954206ec910cf8 was also for "MJIT_SUPPORT"
too.
|
|
because Solaris might have CC=cc and we'd like to check full path
MJIT_CC=/opt/developerstudio12.5/bin/cc instead.
|