| Age | Commit message (Collapse) | Author |
|
If we don't intend to support this platform, we should probably enable
MJIT for MinGW. However, since the code for https://bugs.ruby-lang.org/issues/18439
is in place, I'm adjusting the test for it in the meantime.
following up https://github.com/ruby/ruby/pull/5363
|
|
* Fix test_rubyoptions for MinGW
follows up a74a2f456ad549025861be80f50cc3f0dd6646dd
* Require jit_support
* Fix MinGW platform
* Handle MinGW UCRT
and fix the prefix
* Make it more robust
Notes:
Merged-By: k0kubun <takashikkbn@gmail.com>
|
|
|
|
This was probably not intended in 85a426dc8678f04a78ffd799943b690ce2984c49.
|
|
|
|
|
|
https://github.com/rubygems/rubygems/commit/a053b7e4d4
|
|
`rubygems-update` version
https://github.com/rubygems/rubygems/commit/b0badcd00a
|
|
To see if we get more information when this fails.
https://github.com/rubygems/rubygems/commit/853d33fdc3
|
|
This makes it easier to test the upgrade process locally and should be
more efficient in certain cases where the user has already upgraded in
the past.
https://github.com/rubygems/rubygems/commit/ed6cc88494
|
|
https://github.com/ruby/drb/commit/9a1ff286bc
|
|
|
|
|
|
|
|
- prerequisite of supporting YJIT with VC++.
- note that now can specfily `--yjit` on mswin64, but not enabled
YJIT'ed code because of YJIT requires `OPT_DIRECT_THREADED_CODE`
or `OPT_CALL_THREADED_CODE` in `rb_yjit_compile_iseq`.
|
|
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/5350
|
|
https://github.com/rubygems/rubygems/commit/fa8455ef7c
Notes:
Merged: https://github.com/ruby/ruby/pull/5350
|
|
https://github.com/rubygems/rubygems/commit/7cf0a8fa8e
Notes:
Merged: https://github.com/ruby/ruby/pull/5350
|
|
https://github.com/rubygems/rubygems/commit/a581a1dd50
Notes:
Merged: https://github.com/ruby/ruby/pull/5350
|
|
Since we're at it. This generates a bunch of warnings and seems like a
brittle way to test things, so let's get rid of it.
https://github.com/rubygems/rubygems/commit/f5d45520e0
Notes:
Merged: https://github.com/ruby/ruby/pull/5350
|
|
These specs were monkeypatching `RUBY_VERSION`, but that obviously
doesn't change the running ruby to behave any different.
The removal of some features, in particular, `String#untaint`, made
these specs fail, because untaint is no longer available under ruby-core
and bundler calls `untaint` when `RUBY_VERSION` is less than "2.7",
which these specs were overwriting it to be.
Rewrite these specs to not overwrite `RUBY_VERSION`, but still test the
same things.
https://github.com/rubygems/rubygems/commit/e8c7b92901
Notes:
Merged: https://github.com/ruby/ruby/pull/5350
|
|
It reduces memory usage about 204kb (1.4%).
https://github.com/rubygems/rubygems/commit/b7d4b8c8a6
Notes:
Merged: https://github.com/ruby/ruby/pull/5350
|
|
Probably `RUBY_VERSION` seems overwritten somewhere in the tests.
Notes:
Merged: https://github.com/ruby/ruby/pull/5349
Merged-By: nobu <nobu@ruby-lang.org>
|
|
|
|
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/5348
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/5348
|
|
Also enable the warning for T_DATA allocator.
Notes:
Merged: https://github.com/ruby/ruby/pull/5348
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/5348
|
|
Already these had been announced to be removed in 3.2.
Notes:
Merged: https://github.com/ruby/ruby/pull/5348
|
|
|
|
[Bug #18434]
Notes:
Merged: https://github.com/ruby/ruby/pull/5347
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This reverts commit a042043487eb4c7d39307b8e784ede1856455c3e.
|
|
|
|
This reverts commit afa9d65d61857792508b1405835b07b78e24449c.
It prevents installing libffi.
|
|
Pass ruby directory path
|
|
|
|
https://github.com/ruby/io-console/commit/806c65e22b
|
|
https://github.com/ruby/io-console/commit/e9478509e9
|
|
Show an example of Time.new with perhaps unexpected results in
earlier versions.
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/5345
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/5345
|