Age | Commit message (Collapse) | Author |
|
https://github.com/ruby/etc/commit/25c538120c
|
|
This reverts commit 69f698d85ada116db5747873e53c597991bedff8.
Again.
|
|
This reverts commit 5885550c8cb80fb8784598d3af1d90823f4f6604.
It didn't work without `--enable-shared`.
|
|
|
|
|
|
https://github.com/ruby/etc/commit/25c538120c
|
|
This reverts commit 919b175afc389f8df6a3caa05ffdd28f5fc4bfca.
Since 604689628dc64d050a68f1ebe5e06f9105474936, to let `try_run`
work before LIBRUBY_SO is installed, `try_link` links against the
static library which defines even symbols unexported in the shared
library.
|
|
https://github.com/ruby/etc/commit/25c538120c
|
|
Revert "Added build:mingw" e1674c18f5a0faf881b362363f428d139baef3b4.
https://github.com/ruby/etc/commit/d8f1dd85d3
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/2892
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/2892
|
|
to eliminate sp / pc moves by cancelling JIT execution on interrupts.
$ benchmark-driver benchmark.yml -v --rbenv 'before --jit;after --jit' --repeat-count=12 --output=all
before --jit: ruby 2.8.0dev (2020-04-01T03:48:56Z master 5a81562dfe) +JIT [x86_64-linux]
after --jit: ruby 2.8.0dev (2020-04-01T04:58:01Z master 39beb26a27) +JIT [x86_64-linux]
Calculating -------------------------------------
before --jit after --jit
Optcarrot Lan_Master.nes 75.06409603894944 76.06422026555558 fps
75.12025067279242 78.48161731616810
77.42020273492177 79.78958240950033
79.07253675128945 79.88645902325614
79.99179109732327 80.33743931749331
80.07633091008627 80.53790081529166
80.15450942667547 80.99048270668010
80.48372803283709 81.70497146081003
80.57410149187352 82.79494539467382
81.80449157081202 82.85797792223954
82.24629397834902 83.00603891515506
82.63708148686703 83.23221006969828
$ benchmark-driver -v --rbenv 'before;before --jit;after --jit' benchmark/mjit_leave.yml --repeat-count=4
before: ruby 2.8.0dev (2020-04-01T03:48:56Z master 5a81562dfe) [x86_64-linux]
before --jit: ruby 2.8.0dev (2020-04-01T03:48:56Z master 5a81562dfe) +JIT [x86_64-linux]
after --jit: ruby 2.8.0dev (2020-04-01T04:58:01Z master 39beb26a27) +JIT [x86_64-linux]
Calculating -------------------------------------
before before --jit after --jit
mjit_leave 106.656M 82.786M 91.635M i/s - 200.000M times in 1.875183s 2.415881s 2.182569s
Comparison:
mjit_leave
before: 106656239.9 i/s
after --jit: 91635143.7 i/s - 1.16x slower
before --jit: 82785537.2 i/s - 1.29x slower
|
|
It is not needed to test itself, but the element should be tested
instead.
|
|
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/2995
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/2995
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/2995
|
|
Resize string buffer only if some data is received in
BasicSocket#read_nonblock and some methods.
Co-Authored-By: Samuel Williams <samuel.williams@oriontransfer.co.nz>
|
|
|
|
It originally had a string literal, but it no longer has one.
|
|
|
|
JIT support of dd723771c11.
$ benchmark-driver -v --rbenv 'before;before --jit;after --jit' benchmark/mjit_exivar.yml --repeat-count=4
before: ruby 2.8.0dev (2020-03-30T12:32:26Z master e5db3da9d3) [x86_64-linux]
before --jit: ruby 2.8.0dev (2020-03-30T12:32:26Z master e5db3da9d3) +JIT [x86_64-linux]
after --jit: ruby 2.8.0dev (2020-03-31T05:57:24Z mjit-exivar 128625baec) +JIT [x86_64-linux]
Calculating -------------------------------------
before before --jit after --jit
mjit_exivar 57.944M 53.579M 54.471M i/s - 200.000M times in 3.451588s 3.732772s 3.671687s
Comparison:
mjit_exivar
before: 57944345.1 i/s
after --jit: 54470876.7 i/s - 1.06x slower
before --jit: 53579483.4 i/s - 1.08x slower
|
|
|
|
`--shallow-since=yesterday` for COMMIT_NUMBER_OF_DAY of `tool/actions-commit-info.sh`.
COMMIT_NUMBER_OF_DAY is mainly for master branch.
And `--shallow-since=yesterday` may fail on pull request.
So this revert to `--depth` on pull request.
Notes:
Merged: https://github.com/ruby/ruby/pull/2992
|
|
|
|
|
|
It has been deprecated for 3 years, and has been broken for that entire
period. (It required itself, instead of `rubygems/source/local`.)
Closes #3158.
https://github.com/rubygems/rubygems/commit/2f01a272d0
|
|
Gem::DependencyInstaller#find_gems_with_sources"
This reverts commit 04c79d3eb9d9803d9fae78575b125b325b97206e.
Final removal is postponed until next year until we find a better way to
manage deprecations.
https://github.com/rubygems/rubygems/commit/3e1cf918a5
|
|
That line means that the class supports both `URI`'s and `String`'s
being passed to `initialize`. I don't see how that's related to 1.8.
https://github.com/rubygems/rubygems/commit/77aeff4515
|
|
https://github.com/rubygems/rubygems/commit/84c89275b8
|
|
https://github.com/rubygems/rubygems/commit/6fa0b1b679
|
|
https://github.com/rubygems/rubygems/commit/9e21fe7f58
|
|
https://github.com/rubygems/rubygems/commit/d45cd34a67
|
|
Makes it easier to rubocop.
https://github.com/rubygems/rubygems/commit/26b31248ae
|
|
So it matches the style used by bundler.
https://github.com/rubygems/rubygems/commit/ab0580fd65
|
|
|
|
Since 0c2d81dada, not all trace events are cleared during VM teardown.
This causes a crash when there is a tracepoint for
`RUBY_INTERNAL_EVENT_GC_EXIT` active during teardown.
The commit looks like a refactoring commit so I think this change was
unintentional.
[Bug #16682]
Notes:
Merged: https://github.com/ruby/ruby/pull/2959
|
|
It was moved from defs/gmake.mk at 88f4ebac83a, for use in
dependency rule lines.
|
|
`time_with_zone.zone.should == (time_with_zone - 60*60).zone` fails when
the time is immediately before the change of summer time.
https://rubyci.org/logs/rubyci.s3.amazonaws.com/unstable11s/ruby-master/log/20200328T232504Z.fail.html.gz
```
1)
Time#+ preserves time zone FAILED
Expected "CET" == "CEST"
to be truthy but was false
```
It is acceptable as it fails at most twice per year, but it would be
good to use near time objects to reduce the possibility.
|
|
|
|
CI of 5806c54447439f2ba22892e4045e78dd80f96f0c did not succeed
https://travis-ci.org/github/ruby/ruby/jobs/668072714
|
|
|
|
|
|
https://github.com/ruby/irb/commit/dc59afe4f6
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/2988
|
|
|
|
* Since the spec might not spend any time in system calls.
|
|
|
|
* Otherwise it might segfault, since C has no idea of the type of varargs,
and the C code must assume all varargs are VALUE.
|
|
* Almost all platforms return incorrect values for Process.clock_getres,
it should be removed: https://bugs.ruby-lang.org/issues/16740
|