Age | Commit message (Collapse) | Author |
|
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/5006
|
|
benchmark for a class's ivar setter
Notes:
Merged: https://github.com/ruby/ruby/pull/5006
|
|
if an ivar of a class/module refer to a shareable object, this ivar
can be read from non-main Ractors.
Notes:
Merged: https://github.com/ruby/ruby/pull/5006
|
|
`URI.parse('https://a.b.c/')` needs 'uri/https'.
|
|
844588f9157b364244a7d34ee0fcc70ccc2a7dd9 made it so that trying to call
gc_verify_compaction_references on unsupported platform result in an
exception rather than a crash. Rescue the exception in a YJIT btest
that uses gc_verify_compaction_references.
Notes:
Merged: https://github.com/ruby/ruby/pull/5004
Merged-By: XrXr
|
|
https://github.com/ruby/mutex_m/commit/a839e29d04
|
|
(https://github.com/ruby/uri/pull/30)
https://github.com/ruby/uri/commit/bf13946c32
Co-authored-by: Samuel Williams <samuel.williams@oriontransfer.co.nz>
|
|
https://github.com/ruby/delegate/commit/81a3c32140
|
|
MacOs concurrency on GitHub Actions is limited, and the
performance is relatively poor.
|
|
|
|
|
|
|
|
|
|
|
|
--enable=all didn't work when cppflags=-DMJIT_FORCE_ENABLE was given.
|
|
It seems like `gc_verify_compaction_references` is not protected in case
alignment is wrong. This commit pushes the alignment check down to
`gc_start_internal` so that anyone trying to compact will check page
alignment
I think this method may be getting called on PowerPC and the alignment
might be wrong.
http://rubyci.s3.amazonaws.com/ppc64le/ruby-master/log/20211021T190006Z.fail.html.gz
Notes:
Merged: https://github.com/ruby/ruby/pull/5001
|
|
2d98593bf54a37397c6e4886ccc7e3654c2eaf85 made it so that
attr_accessor methods fire C method tracing events.
Previously, we weren't checking for whether we are tracing before
compiling, leading to missed events.
Since global invalidation invalidates all code, and that attr_accessor
methods can never enable tracing while running, events are only dropped
when YJIT tries to compile when tracing is already enabled.
Factor out the code for checking tracing and check it before generating
code for attr_accessor methods.
This change fixes TestSetTraceFunc#test_tracepoint_attr when it's
ran in isolation.
Notes:
Merged-By: maximecb
|
|
I am not sure why this flag was turned off (it wasn't explained in my commit message in 0365dc852767ae589376a7aad1fb129738e408b0 or in my PR in #4411).
Whatever the reason, without `default_ignores` turned on, most default CI configurations will immediately fail, as they most likely vendor and cache their dependencies under `vendor`, which will cause standard to run against all the vendored gems and (most likely) fail. I think we should remove this before this feature is released.
https://github.com/rubygems/rubygems/commit/677f74be48
|
|
Requested by @nurse
|
|
|
|
TestRubyOptions#test_enable was broken on OpenBSD after the yjit
merge. --yjit (and --enable-all, which enables --yjit) fails on
OpenBSD because yjit uses an insecure mmap call (both writable
and executable), in alloc_exec_mem, which OpenBSD does not allow.
This can probably be reverted if yjit switches to a more secure
mmap design (writable xor executable). This would involve
initially calling mmap with PROT_READ | PROT_WRITE, and after writing
of executable code has finished, using mprotect to switch to
PROT_READ | PROT_EXEC. I believe Firefox uses this approach for
their Javascript engine since Firefox 46.
|
|
|
|
|
|
|
|
https://github.com/ruby/prettyprint/commit/0e8eee5f5f
|
|
https://github.com/ruby/pp/commit/06b839b9ca
|
|
https://github.com/ruby/securerandom/commit/5f9d3d1dfa
|
|
https://github.com/ruby/rinda/commit/d394ba107e
|
|
https://github.com/ruby/optparse/commit/1226b670e6
|
|
https://github.com/ruby/net-http/commit/f3e65e2a31
|
|
https://github.com/ruby/net-protocol/commit/088e52609a
|
|
https://github.com/ruby/uri/commit/1619f713e6
|
|
https://github.com/ruby/ostruct/commit/c535a406f8
|
|
https://github.com/ruby/io-wait/commit/f6a1b10a59
|
|
https://github.com/ruby/stringio/commit/f7c40aa339
|
|
https://github.com/ruby/fileutils/commit/918d19e4f2
|
|
instead
Refinement#import_methods imports methods from modules.
Unlike Module#include, it copies methods and adds them into the refinement,
so the refinement is activated in the imported methods.
[Bug #17429] [ruby-core:101639]
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/4913
|
|
`RubyVM.keep_script_lines` enables to keep script lines
for each ISeq and AST. This feature is for debugger/REPL
support.
```ruby
RubyVM.keep_script_lines = true
RubyVM::keep_script_lines = true
eval("def foo = nil\ndef bar = nil")
pp RubyVM::InstructionSequence.of(method(:foo)).script_lines
```
Notes:
Merged: https://github.com/ruby/ruby/pull/4913
|
|
|
|
While f6048e592c520e20ba498ba4d553f07f02213a61 tried to approach the
instability mentioned there, unfortunately the Travis arm32 environment
seems unstable by itself. I already saw 2 different failures in the last
4 builds:
https://app.travis-ci.com/github/ruby/ruby/jobs/544382885
https://app.travis-ci.com/github/ruby/ruby/jobs/544361370
Let's revisit this when this kind of thing stops happening.
|
|
https://github.com/ruby/psych/commit/69a713f860
|
|
|
|
|
|
|
|
https://github.com/ko1/build-ruby/commit/0dbd95c6250594b6ddadc3c4424b071704083187
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/4997
|
|
|
|
Fixes:
./src/yjit_asm.c:196:8: warning: 'mem_block' may be used uninitialized [-Wmaybe-uninitialized]
|