| Age | Commit message (Collapse) | Author |
|
Write barriers may be required when VM_ENV_FLAG_WB_REQUIRED is set,
however write barriers only affect heap objects being written. If we
know an immediate value is being written we can skip this check.
Notes:
Merged-By: maximecb <maximecb@ruby-lang.org>
|
|
In test_bug_reporter and test_rubyoptions we intentionally
test child processes that cause SEGV. We run them with YJIT
if the parent uses YJIT so that the text description
matches the parent RUBY_DESCRIPTION.
Notes:
Merged-By: maximecb <maximecb@ruby-lang.org>
|
|
In wmap_live_p, if is_pointer_to_heap returns false, then the page is
either in the tomb or has already been freed, so the object is dead. In
this case, wmap_live_p should return false.
Notes:
Merged: https://github.com/ruby/ruby/pull/6152
|
|
Running a command like that is actually removing any previous default
bundler specs in the default RubyGems installation (outside of destdir).
It should instead only modify destdir.
https://github.com/rubygems/rubygems/commit/5ed275383c
|
|
https://github.com/rubygems/rubygems/commit/ca956c0de2
|
|
https://github.com/rubygems/rubygems/commit/6012800a20
|
|
https://github.com/rubygems/rubygems/commit/e5434be14c
|
|
Specifying multiple primary sources in top-level was deprecated in
Bundler 1.13.
As Bundler CLI uses primary source instead of global, "global source"
is replaced with "primary source".
Co-authored-by: David Rodríguez <deivid.rodriguez@riseup.net>
Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>
https://github.com/rubygems/rubygems/commit/1dd1753f6e
|
|
Free objects have `T_NONE` as the builtin type. A pointer to a valid
array element will never be `NULL`.
Notes:
Merged: https://github.com/ruby/ruby/pull/6153
Merged-By: nobu <nobu@ruby-lang.org>
|
|
```elisp
(mmm-ify-by-regexp 'ruby-mode
"^ *#!.*ruby" 0 "^ *shell: *ruby.*{0}" 0 0)
```
|
|
`RbConfig::CONFIG["ENABLE_SHARED"]`
https://github.com/rubygems/rubygems/commit/3d1ae0050b
|
|
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6149
|
|
global sources
Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>
https://github.com/rubygems/rubygems/commit/316564b8fc
|
|
rb_str_modify clear the coderange, which in this case isn't
necessary.
```
compare-ruby: ruby 3.2.0dev (2022-07-12T15:01:11Z master 71aec68566) [arm64-darwin21]
built-ruby: ruby 3.2.0dev (2022-07-19T07:17:01Z faster-buffer-conc.. 3cad62aab4) [arm64-darwin21]
warming up...
| |compare-ruby|built-ruby|
|:---------------------|-----------:|---------:|
|binary_concat_utf8 | 360.617k| 605.091k|
| | -| 1.68x|
|binary_concat_binary | 446.650k| 605.053k|
| | -| 1.35x|
|utf8_concat_utf8 | 454.166k| 597.311k|
| | -| 1.32x|
```
```
| |compare-ruby|built-ruby|
|:-----------|-----------:|---------:|
|erb_render | 1.790M| 2.045M|
| | -| 1.14x|
```
Notes:
Merged: https://github.com/ruby/ruby/pull/6120
|
|
If the LHS is ASCII compatible and the RHS is 7BIT
we can directly concat without being concerned about
anything else.
Benchmark:
```
compare-ruby: ruby 3.2.0dev (2022-07-12T15:01:11Z master 71aec68566) [arm64-darwin21]
built-ruby: ruby 3.2.0dev (2022-07-13T10:13:53Z faster-buffer-conc.. a04c10476d) [arm64-darwin21]
warming up...
| |compare-ruby|built-ruby|
|:---------------------|-----------:|---------:|
|binary_append_utf8 | 385.315k| 573.663k|
| | -| 1.49x|
|binary_append_binary | 446.579k| 574.898k|
| | -| 1.29x|
|utf8_append_utf8 | 430.936k| 573.394k|
| | -| 1.33x|
```
Note that in the benchmark, the RHS always have a precomputed
coderange. So the benchmark never enter the slowpath of having to
scan the RHS. However it's extremly likely that we'll end
up scanning it anyway in rb_enc_cr_str_buf_cat
Notes:
Merged: https://github.com/ruby/ruby/pull/6120
|
|
https://github.com/ruby/fileutils/commit/332025bc02
Co-Authored-By: David Rodríguez <deivid.rodriguez@riseup.net>
|
|
Otherwise it's way too easy to confuse it with US_ASCII.
Notes:
Merged: https://github.com/ruby/ruby/pull/6127
|
|
This allows us to treat cvar caches differently than ivar caches.
Notes:
Merged: https://github.com/ruby/ruby/pull/6148
|
|
/test/rubygems/test_gem_ext_cargo_builder/custom_name
Bumps [rb-sys](https://github.com/oxidize-rb/rb-sys) from 0.9.19 to 0.9.20.
- [Release notes](https://github.com/oxidize-rb/rb-sys/releases)
- [Commits](https://github.com/oxidize-rb/rb-sys/compare/v0.9.19...v0.9.20)
---
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/2689b6b940
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/5978
|
|
|
|
Bumps [rb-sys](https://github.com/oxidize-rb/rb-sys) from 0.9.19 to 0.9.20.
- [Release notes](https://github.com/oxidize-rb/rb-sys/releases)
- [Commits](https://github.com/oxidize-rb/rb-sys/compare/v0.9.19...v0.9.20)
---
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/ee2facb8f2
|
|
vshared is no longer used.
|
|
If directories are already created (the common case), fileutils won't be
required at all.
https://github.com/rubygems/rubygems/commit/63a9b94fc9
|
|
deduplicate_call_seq has a bug that skips call-seq for methods where the
alias is a prefix of the method name. For example, if the alias name is
"each" and the current method name is "each_line", then
deduplicate_call_seq will skip all call-seq for "each_line" since it
will believe that it is for the alias.
https://github.com/ruby/rdoc/commit/1148988ccc
|
|
https://github.com/rubygems/rubygems/commit/16d01f9486
|
|
Include the source of each gem.
https://github.com/rubygems/rubygems/commit/a0bed2fb79
|
|
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6146
Merged-By: nobu <nobu@ruby-lang.org>
|
|
Creates simple bin stubs to load the extracted executable files.
After only extracted under `gems` directory, the gems are considered
installed but the executable scripts are not found.
Also the second argument is now the parent of the previous second and
third arguments.
Notes:
Merged: https://github.com/ruby/ruby/pull/6145
|
|
WASI doesn't guarantee that `/dev/null` is present.
So without this patch, we needed to mount host's `/dev` directory to WASI
guest process to avoid `ENOTCAPABLE` error while `require "bundler/setup"`
https://github.com/rubygems/rubygems/commit/e9187ab61f
|
|
Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>
https://github.com/rubygems/rubygems/commit/e11f5a143b
|
|
Instead of showing the bug report template.
https://github.com/rubygems/rubygems/commit/0c8b6f7dd5
|
|
https://github.com/rubygems/rubygems/commit/972e8ff965
|
|
extensions
https://github.com/rubygems/rubygems/commit/5ecc0e0b31
|
|
|
|
|
|
|
|
|
|
`specification_version` method was added before RubyGems 1.0, and
`add_runtime_dependency` method was before 1.2. These seem aged
enough to remove.
https://github.com/rubygems/rubygems/commit/92770c5cd9
|
|
|
|
|
|
|
|
This script runs `make` internally, and sub-`make`s need the
environment variable for the job server when compiling in parallel.
|
|
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6144
|
|
Add send unit tests for YJIT
Notes:
Merged-By: maximecb <maximecb@ruby-lang.org>
|
|
|
|
As pointed out in the
[comment](https://github.com/ruby/reline/pull/413#issuecomment-1168033973),
the code is actually a control sequence and not only for colors.
To make the dialog color APIs safer to use, we should restrict its
usages and extract away the bg/fg concept from the input.
So in this commit, I made these changes:
1. The dialog_*_bg/fg_color APIs only takes and returns color names (symbol):
- :black
- :red
- :green
- :yellow
- :blue
- :magenta
- :cyan
- :white
2. Add additional dialog_*_bg/fg_color_sequence APIs to access the raw code.
https://github.com/ruby/reline/commit/b32a977766
|