Age | Commit message (Collapse) | Author |
|
When target_alias is not empty, `-gnu` suffixed is not stripped.
[Bug #16015]
|
|
[ci skip]
|
|
|
|
[Misc #15806]
Closes: https://github.com/ruby/ruby/pull/2128
|
|
[Misc #15806]
Closes: https://github.com/ruby/ruby/pull/2128
|
|
|
|
|
|
[Feature #15805]
Closes: https://github.com/ruby/ruby/pull/2140
|
|
|
|
|
|
|
|
Fixes [Bug #10422]
|
|
Also, remove documentation about returning self, which makes no
sense as self would be the Regexp class. It could be interpreted
as return the argument if no changes were made, but that hasn't
been the behavior at least since 1.8.7 (and probably before).
Fixes [Bug #10239]
|
|
Mention how each of the arguments are retrievable from the generated
Exception object.
Fixes [Bug #10110]
|
|
|
|
By using `BITFIELD`, `type` field should not be forced to align.
|
|
|
|
Fixes [Bug #10025]
|
|
|
|
Same as last commit, make some fields `const`.
include/ruby/ruby.h:
* Rasic::klass
* RArray::heap::aux::shared_root
* RRegexp::src
internal.h:
* rb_classext_struct::origin_, redefined_class
* vm_svar::cref_or_me, lastline, backref, others
* vm_throw_data::throw_obj
* vm_ifunc::data
* MEMO::v1, v2, u3::value
While modifying this patch, I found write-barrier miss on
rb_classext_struct::redefined_class.
Also vm_throw_data::throw_state is only `int` so change the type.
|
|
https://github.com/ruby/date/commit/8eca79d1f0
|
|
RHash::ifnone should be protected by write-barriers so this field
should be const. However, to introduce GC.compact, the const was
removed. This commit revert this removing `const` and modify
gc.c `TYPED_UPDATE_IF_MOVED` to remove `const` forcely by a type cast.
|
|
|
|
Raise the proper exception when that option is not given but
non-option argument is.
|
|
|
|
|
|
|
|
And `make test-tool` includes `make test-testframework`.
This change may be arguable because I'm unsure who is an intended user
of `make check`: a normal user, or Ruby-core developer. Normal users
don't have to run `make test-tool` for testing their installation, but
Ruby committers should run it before they commit anything.
In this case, I'd be conservative; `make check` includes `test-tool`.
If normal users often report a failure of `make test-tool`, then we can
consider to split `make check` for two sets of target users.
|
|
tool/test/runner.rb had been copied from test/runner.rb.
test/runner.rb was for `make test-all`, and tool/test/runner.rb was for
`make test-testframework` and `make test-tool`.
But I want to avoid the code clones.
This change makes tool/test/runner.rb support --test-target-dir option
which allows tool/test/runner.rb to run `make test-all`.
Now we can remove test/runner.rb.
|
|
|
|
|
|
|
|
Even after 19d592dc82a31adf0bb6f027392cae69615c2394, the retry seems not
functional. Let's just add --debug from the beginning because an output
of each step is collapsed and we don't see `make up` output so often.
|
|
clang complains the lack.
|
|
I'm actually not using this, but ko1 is.
|
|
because v0.14.18 was actually not working with `make run`.
In `make run`, `Gem` is defined but `Gem::Version` isn't.
v0.14.19 checks `defined?(Gem::Version)` instead of `defined?(Gem)`.
|
|
This is to make `make run` with benchmark/lib/load.rb work for ko1
https://github.com/benchmark-driver/benchmark-driver/compare/v0.14.17...v0.14.18
|
|
ARY_SHARED_P and ARY_EMBED_P included:
assert(!FL_TEST((ary), ELTS_SHARED) || !FL_TEST((ary), RARRAY_EMBED_FLAG)),
The two predicate macros are used in many other assert conditions,
which caused memory bloat during C compilation.
This change factors out the assertion above to a function.
Now gcc consumes 160 MB instead of 250 MB to compile array.c.
|
|
This is the only place that can change the size of the object id tables
and cause a GC.
|
|
|
|
Improvements in Ruby 2.5 and 2.6 make this section no longer
accurate.
|
|
This support is now deprecated and will be removed in Ruby 3.
|
|
Fixes [Misc #8905]
|
|
Fixes [Bug #8952]
|
|
|
|
|
|
The old code lost information of lineno. Now, an assertion error will
output a correct lineno (but now gcc 8 requires 250 MB, unfortunately).
|
|
The assertion blows up gcc 8 by consuming approx. 1.8 GB memory.
This change reduces the amount of memory required to about 200 MB.
A follow-up of ae750799c1b28b06d02e50cd26450b9903516526.
|
|
|
|
"Therefore, `fiber_pool_stack_free(&vacancy->stack)` can do the wrong
thing..." should be "... `fiber_pool_stack_free(stack)` ...".
|