Age | Commit message (Collapse) | Author |
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
This concatenation of string literals is to not empty the array
initialization even if no counter is declared, but warned by clang as
suspicious.
|
|
|
|
https://github.com/ruby/pstore/commit/cb2b9dc9a9
|
|
https://github.com/ruby/pstore/commit/7e56730689
|
|
https://github.com/ruby/pstore/commit/23a7f5468f
|
|
https://github.com/ruby/pstore/commit/c12560e59a
|
|
https://github.com/ruby/pstore/commit/117177c226
|
|
https://github.com/ruby/pstore/commit/8f9843ef19
|
|
https://github.com/ruby/pstore/commit/8de41c1eed
|
|
https://github.com/ruby/pstore/commit/c59d4a063e
|
|
https://github.com/ruby/pstore/commit/81a266d88c
|
|
https://github.com/rubygems/rubygems/commit/b93d4de2ff
|
|
https://github.com/rubygems/rubygems/commit/6aa4c422a7
|
|
Use the value as similar as other tests below.
Trying to fix sporadic “not yet valid” failures on some CIs.
Notes:
Merged: https://github.com/ruby/ruby/pull/6085
|
|
Usually, command line options are given precedence first, environment
variables next, and fall back to configuration options at last.
Notes:
Merged: https://github.com/ruby/ruby/pull/6080
|
|
https://github.com/ruby/bigdecimal/commit/3ede8860a6
|
|
|
|
This new page would be linked from method strftime in Time, Date, and DateTime, replacing the text there.
Notes:
Merged-By: BurdetteLamar <BurdetteLamar@Yahoo.com>
|
|
|
|
|
|
Update RBS to v2.6.0 and specify RBS commit hash to fix test failure on test-bundled-gems
Notes:
Merged-By: pocke <p.ck.t22@gmail.com>
|
|
|
|
|
|
302f353fd9223d020e48495eaa7a03ce5d539409 seems break the rubyspec.
@nobu please check it.
|
|
|
|
https://github.com/ruby/stringio/commit/16847fea32
|
|
Refactor gen_opt_mod in YJIT
Notes:
Merged-By: maximecb <maximecb@ruby-lang.org>
|
|
handle case in YJIT stats where 0 exits causes NaN in the display
Notes:
Merged-By: maximecb <maximecb@ruby-lang.org>
|
|
https://github.com/rubygems/rubygems/commit/b1826876d0
|
|
http://rubyci.s3.amazonaws.com/ubuntu2004-arm/ruby-master/log/20220630T063003Z.log.html.gz
```
[19606/21662] TestAst#test_not_cared:test/rubygems/test_gem_ext_cargo_builder/custom_name/build.rb(none):18: warning: `*' interpreted as argument prefix
(none):19: warning: `*' interpreted as argument prefix
= 0.00 s
```
https://github.com/rubygems/rubygems/commit/c98f9326e8
|
|
Statically determined value should be set statically.
|
|
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6065
|
|
|
|
If `XDG_RUNTIME_DIR` is available, test-bundled-gems fails with
old debug.gem tests.
Notes:
Merged: https://github.com/ruby/ruby/pull/6081
|
|
|
|
This allows us to delete the disassembly code path for reference
updating.
Notes:
Merged: https://github.com/ruby/ruby/pull/6062
|
|
This function shouldn't leak and is only needed during instruction
assembly
Notes:
Merged: https://github.com/ruby/ruby/pull/6069
|
|
We need to dump relative offsets for inline storage entries so that
loading iseqs as an array works as well. This commit also has some
minor refactoring to make computing relative ISE information easier.
This should fix the iseq dump / load as array tests we're seeing fail in
CI.
Co-Authored-By: John Hawthorn <john@hawthorn.email>
Notes:
Merged: https://github.com/ruby/ruby/pull/6069
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6077
|
|
https://github.com/rubygems/rubygems/commit/3f83236c02
|
|
This fails if there are any unused rust-bindgen "allow" entries. For
that target we turn on Rust warnings (there are a lot) and grep for the
ones that correspond to unused allow entries.
I've added check-yjit-bindgen-unused as a dependency of
check-yjit-bindings, so unused allow entries will now fail CI.
This change also removes our single unused allow entry (VM_CALL.*) which
was known to be bad.
Notes:
Merged-By: maximecb <maximecb@ruby-lang.org>
|
|
|
|
|