| Age | Commit message (Collapse) | Author |
|
https://github.com/rubygems/rubygems/commit/89362c18ef
Co-authored-by: Mike Dalessio <mike.dalessio@gmail.com>
|
|
I think this highlights better how musl is special.
https://github.com/rubygems/rubygems/commit/4075771697
|
|
Before d594a5a8bd0756f65c078fcf5ce0098250cba141, we were only
asserting that the value on an ivar_get was ractor_sharable if the
object was a T_OBJECT and also ractor shareable. We should still
be doing this check only if the object is a T_OBJECT and ractor
shareable
Notes:
Merged: https://github.com/ruby/ruby/pull/6477
|
|
https://github.com/ruby/irb/commit/45b539af39
|
|
Notes:
Merged-By: maximecb <maximecb@ruby-lang.org>
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6353
Merged-By: nobu <nobu@ruby-lang.org>
|
|
|
|
https://github.com/rubygems/rubygems/commit/ec3fd55d40
|
|
Which controls the timezone offset for `RUBY_RELEASE_DATE`.
Notes:
Merged: https://github.com/ruby/ruby/pull/6473
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6473
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6473
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6473
|
|
* So it's easy to review https://github.com/ruby/ruby/pull/6242 +
https://github.com/ruby/ruby/pull/6467 and there are less changes
overall.
|
|
removed
Notes:
Merged: https://github.com/ruby/ruby/pull/6467
|
|
* See https://bugs.ruby-lang.org/issues/18729#note-34
* See [Bug #18729]
Notes:
Merged: https://github.com/ruby/ruby/pull/6467
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6467
|
|
* We need to resolve the zsuper method first, and then look the super
method of that.
Notes:
Merged: https://github.com/ruby/ruby/pull/6467
|
|
RARRAY_PTR when called with a transient array detransients the array
before returning its pointer which allocates in the heap.
Because RARRAY_PTR was being used during compaction (when re-embedding
arrays that have moved between size pools) this introduces the
possibility that we can hit a malloc threshold, triggering GC, while in
the middle of compaction.
We should avoid this by using safer functions to get hold of the
pointer. Since we know that the array is not embedded here, we can use
ARY_HEAP_PTR and ARY_EMBED_PTR directly
Notes:
Merged: https://github.com/ruby/ruby/pull/6466
|
|
|
|
|
|
just the host
https://github.com/rubygems/rubygems/commit/46990f3292
|
|
fetcher.data[:path]
https://github.com/rubygems/rubygems/commit/4d91cacb1f
Co-authored-by: Jacques Chester <jacques.chester@shopify.com>
|
|
https://github.com/rubygems/rubygems/commit/da7837630b
|
|
https://github.com/rubygems/rubygems/commit/ccca30c77a
Co-authored-by: Nick Schwaderer <nick.schwaderer@shopify.com>
|
|
http://rubyci.s3.amazonaws.com/solaris10-gcc/ruby-master/log/20220929T050003Z.fail.html.gz
|
|
Th buffer size is small enough and no need to allocate dynamically.
https://github.com/ruby/date/commit/f62bf0a01d
|
|
|
|
https://github.com/ruby/date/commit/f51b038074
|
|
|
|
|
|
|
|
|
|
|
|
So that it's found when needed, rather than dynamically modifying
loaded stubs and thus messing with RubyGems internals.
https://github.com/rubygems/rubygems/commit/cd3e7cb9e5
|
|
Loading Bundler beforehand was actually replacing ENV with a backup of
the pre-Bundler environment through `Bundler::EnvironmentPreserver`. I
think that was making a bug in `ENV.replace` not bite our tests, because
Bundler includes proper patches to workaround that issue. So this commit
also includes these patches in RubyGems tests.
https://github.com/rubygems/rubygems/commit/8e079149b9
|
|
`Gem::Specification#load_paths` is actually a Bundler thing.
https://github.com/rubygems/rubygems/commit/d20b4d1950
|
|
https://github.com/rubygems/rubygems/commit/3934deb4e4
|
|
https://github.com/rubygems/rubygems/commit/6c0c02c533
|
|
The `$LOAD_PATH` should be properly setup so that the local version is
used.
https://github.com/rubygems/rubygems/commit/03c0ab4082
|
|
https://github.com/rubygems/rubygems/commit/4bd77488ad
|
|
https://github.com/rubygems/rubygems/commit/2e05dadbc5
|
|
https://github.com/rubygems/rubygems/commit/d86a5ae2eb
|
|
|
|
|
|
We don't allocate shapes out of the GC anymore, so we shouldn't mark
those pointers.
|
|
Tabs were expanded because the file did not have any tab indentation in unedited lines.
Please update your editor config, and use misc/expand_tabs.rb in the pre-commit hook.
|
|
Object Shapes is used for accessing instance variables and representing the
"frozenness" of objects. Object instances have a "shape" and the shape
represents some attributes of the object (currently which instance variables are
set and the "frozenness"). Shapes form a tree data structure, and when a new
instance variable is set on an object, that object "transitions" to a new shape
in the shape tree. Each shape has an ID that is used for caching. The shape
structure is independent of class, so objects of different types can have the
same shape.
For example:
```ruby
class Foo
def initialize
# Starts with shape id 0
@a = 1 # transitions to shape id 1
@b = 1 # transitions to shape id 2
end
end
class Bar
def initialize
# Starts with shape id 0
@a = 1 # transitions to shape id 1
@b = 1 # transitions to shape id 2
end
end
foo = Foo.new # `foo` has shape id 2
bar = Bar.new # `bar` has shape id 2
```
Both `foo` and `bar` instances have the same shape because they both set
instance variables of the same name in the same order.
This technique can help to improve inline cache hits as well as generate more
efficient machine code in JIT compilers.
This commit also adds some methods for debugging shapes on objects. See
`RubyVM::Shape` for more details.
For more context on Object Shapes, see [Feature: #18776]
Co-Authored-By: Aaron Patterson <tenderlove@ruby-lang.org>
Co-Authored-By: Eileen M. Uchitelle <eileencodes@gmail.com>
Co-Authored-By: John Hawthorn <john@hawthorn.email>
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6464
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6463
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6463
|