| Age | Commit message (Collapse) | Author |
|
[Bug #18900]
Thread#join and a few other codepaths are using native sleep as
a way to suspend the current thread. So we should call the relevant
hook when this happen, otherwise some thread may transition
directly from `RESUMED` to `READY`.
Notes:
Merged: https://github.com/ruby/ruby/pull/6101
|
|
When similar combination of conditions are separated in two places, it
is harder to make sure the conditional blocks match each other,
Notes:
Merged: https://github.com/ruby/ruby/pull/6100
|
|
If the page_body is a null pointer, then read_barrier_handler will
crash with an unrelated message. This commit improves the error message.
Before:
test.rb:1: [BUG] Couldn't unprotect page 0x0000000000000000, errno: Cannot allocate memory
After:
test.rb:1: [BUG] read_barrier_handler: segmentation fault at 0x14
Notes:
Merged: https://github.com/ruby/ruby/pull/6096
|
|
The page of src could be partially compacted, so it may contain
T_MOVED. Sweeping a page may read objects on this page, so we
need to lock the page.
Notes:
Merged: https://github.com/ruby/ruby/pull/6096
|
|
The page we're sweeping is on the destination heap `dheap`, not the
source heap `heap`.
Notes:
Merged: https://github.com/ruby/ruby/pull/6096
|
|
The (sole) use of memcpy in our public header is now replaced to
directly call ruby_nonempty_memcpy, and the previous definition of
memcpy is now internal-only. [Bug#18893]
Notes:
Merged: https://github.com/ruby/ruby/pull/6098
|
|
|
|
Assume `mkdir -p` to be race-free on recent systems.
And we do not provide install-sh anyway.
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6097
|
|
(https://github.com/ruby/pstore/pull/7)
Modifies RDoc to Emphasize keys instead of roots, values instead of objects.
Code:
Renames method #root? to #key? and method #roots to #keys.
Aliases method #key as #root and method #keys as #roots.
Adds testing for all four methods.
https://github.com/ruby/pstore/commit/4436ea0891
|
|
|
|
All things commercial.
https://github.com/ruby/date/commit/9d3bc61728
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6083
|
|
encodings don't match, as discussed with byroot
Notes:
Merged: https://github.com/ruby/ruby/pull/6095
|
|
`rb_str_concat` does a lot of type checking we can easily bypass.
```
| |compare-ruby|built-ruby|
|:--------------|-----------:|---------:|
|string_concat | 362.007k| 398.965k|
| | -| 1.10x|
```
Notes:
Merged: https://github.com/ruby/ruby/pull/6095
|
|
|
|
Add a counter for gc object refs in the machine code
This is to gather data for the eventual implementation of
a constant pool.
Notes:
Merged-By: maximecb <maximecb@ruby-lang.org>
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6093
Merged-By: nobu <nobu@ruby-lang.org>
|
|
|
|
We no longer need to use older version of binaryen since the blocker
issue has been resolved https://github.com/WebAssembly/binaryen/issues/4401
Notes:
Merged: https://github.com/ruby/ruby/pull/6091
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6087
|
|
they are not installed
https://github.com/rubygems/rubygems/commit/27953ffe9a
|
|
were updated
https://github.com/rubygems/rubygems/commit/4ec608a573
|
|
|
|
So `RbConfig::CONFIG["includedir"]` does not start with double slash.
|
|
|
|
|
|
|
|
It is unrelated to `GlobOption` at all.
|
|
|
|
|
|
|
|
/test/rubygems/test_gem_ext_cargo_builder/custom_name
Bumps [rb-sys](https://github.com/oxidize-rb/rb-sys) from 0.9.15 to 0.9.18.
- [Release notes](https://github.com/oxidize-rb/rb-sys/releases)
- [Commits](https://github.com/oxidize-rb/rb-sys/compare/v0.9.15...v0.9.18)
---
updated-dependencies:
- dependency-name: rb-sys
dependency-type: direct:production
update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>
https://github.com/rubygems/rubygems/commit/a862203683
|
|
Bumps [rb-sys](https://github.com/oxidize-rb/rb-sys) from 0.9.15 to 0.9.18.
- [Release notes](https://github.com/oxidize-rb/rb-sys/releases)
- [Commits](https://github.com/oxidize-rb/rb-sys/compare/v0.9.15...v0.9.18)
---
updated-dependencies:
- dependency-name: rb-sys
dependency-type: direct:production
update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>
https://github.com/rubygems/rubygems/commit/db8486a61e
|
|
|
|
https://github.com/ruby/date/commit/8eb1c780fb
Co-authored-by: Peter Zhu <peter@peterzhu.ca>
|
|
https://github.com/ruby/date/commit/e36690f70e
|
|
https://github.com/ruby/date/commit/dcc0742623
|
|
https://github.com/ruby/date/commit/91c632f156
|
|
https://github.com/ruby/date/commit/5c18ec031e
|
|
https://github.com/ruby/date/commit/fd3ae275c3
|
|
https://github.com/ruby/date/commit/ac25182c66
|
|
https://github.com/ruby/date/commit/f9ecaad2ee
|
|
https://github.com/ruby/date/commit/e80fee4f30
|
|
|
|
I suspect that some shared pages are invalidated because
some static string don't have their coderange set eagerly.
So the first time they are scanned, the entire memory page is
invalidated.
Being able to see the coderange in `ObjectSpace` would help debug
this.
And in addition `dump` currently call `is_broken_string()` and `is_ascii_string()`
which both end up scanning the string and assigning coderange. I think it's
undesirable as `dump` should be read only.
Notes:
Merged: https://github.com/ruby/ruby/pull/6076
|
|
|
|
|
|
This fixes invalid and inconsistent results for the Fixnum*Fixnum case
where the result of the multiplication does not fit in 64-bit
on OpenBSD/mips64. For example:
$ for x in 1 23; do ruby31 -e 'p(54306000000000*86400)'; done
14409380628474329524
11410664325873689790
Cases where an argument was Bignum, as well as cases where the result
of the multiplication fits in 64-bit are fine:
$ for x in 1 23; do ruby31 -e 'p(54306000*86400)'; done
4692038400000
4692038400000
$ for x in 1 23; do ruby31 -e 'p(5430600000000000000000*86400)'; done
469203840000000000000000000
469203840000000000000000000
This was originally discovered by running the tests for the openssl gem
on OpenBSD/mips64 and having one test fail for a date far in the future.
I eventually traced this to the generic multiplication issue.
The underlying cause is using the int128_t type. This avoids use of the
int128_t type in this case, falling back to the slower conversion code,
which in the overflow case, turns the Fixnums into Bignums, then
performs the multiplication.
|
|
|