summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2022-11-14Bump actions/upload-artifact from 3.1.0 to 3.1.1dependabot[bot]
Bumps [actions/upload-artifact](https://github.com/actions/upload-artifact) from 3.1.0 to 3.1.1. - [Release notes](https://github.com/actions/upload-artifact/releases) - [Commits](https://github.com/actions/upload-artifact/compare/3cea5372237819ed00197afe530f5a7ea3e805c8...83fd05a356d7e2593de66fc9913b3002723633cb) --- updated-dependencies: - dependency-name: actions/upload-artifact dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Notes: Merged: https://github.com/ruby/ruby/pull/6723
2022-11-13Refactor update_global_event_hookTakashi Kokubun
It seems more readable to put JIT invalidation code together.
2022-11-13s/mjit_func_t/jit_func_t/Takashi Kokubun
2022-11-13Remove unused debug countersTakashi Kokubun
The structure and readability of jit_exec is messed up right now. I'd like to help the current situation by this for now. I'll resurrect them when I need it again.
2022-11-13YJIT: Instrument global allocations on stats build (#6712)Takashi Kokubun
* YJIT: Instrument global allocations on stats build * Just use GLOVAL_ALLOCATOR.stats() Notes: Merged-By: maximecb <maximecb@ruby-lang.org>
2022-11-13YJIT: Fix invalidation for c_call and c_return (#6719)Alan Wu
Follow-up for 2b8191bdad7545b71f270d2b25a34cd2b3afa02f. Since that commit, we stopped doing code invalidation the second time the call and return events are enabled. We need to do it every time these events are enabled because we might have generated code while these events are disabled. Also rename locals and edit comments to make it more clear that the iseq rewrite code path only happens the first time a particular iseq trace event is enabled. Notes: Merged-By: maximecb <maximecb@ruby-lang.org>
2022-11-13Update yjit.mdMaxime Chevalier-Boisvert
Remove disclaimer
2022-11-13YJIT: Remove unused src_ctx from Block (#6714)Takashi Kokubun
Notes: Merged-By: maximecb <maximecb@ruby-lang.org>
2022-11-13Control non-parallel parts with `.WAIT` if availableNobuyoshi Nakada
2022-11-13[ruby/bigdecimal] Add specific value allocatorsKenta Murata
* Add NewZero* and NewOne* function families * Use them instead of VpAlloc for allocating 0 and 1 https://github.com/ruby/bigdecimal/commit/9276a94ac7
2022-11-13Try to overwrite the file in VPATH if possibleNobuyoshi Nakada
2022-11-13Force to update revision.h when commits differNobuyoshi Nakada
2022-11-12Deal with different Ruby versionsTakashi Kokubun
2022-11-13[ruby/bigdecimal] Add and use specific value allocatorsKenta Murata
* Add rbd_allocate_struct_zero for making 0.0 * Add rbd_allocate_struct_one for making 1.0 * Use them to replace VpAlloc calls * Renmae VpPt5 to VpConstPt5 https://github.com/ruby/bigdecimal/commit/40c826f5e6
2022-11-13[ruby/bigdecimal] Make VPrint function always availableKenta Murata
https://github.com/ruby/bigdecimal/commit/5391f7e92c
2022-11-12Fix a CI failure in bigdecimalTakashi Kokubun
2022-11-13[ruby/bigdecimal] Tweak VpAllocKenta Murata
* Stop reusing mx and mf * Check szVal == NULL first * Treat special values before checking the leading `#` https://github.com/ruby/bigdecimal/commit/14f3d965f8
2022-11-13[ruby/bigdecimal] Rewrite allocation functionsKenta Murata
* Rename them * Make allocation count operations atomic https://github.com/ruby/bigdecimal/commit/a5ab34a115
2022-11-13[ruby/bigdecimal] Twak GetPrecisionInt and rename it to check_int_precisionKenta Murata
https://github.com/ruby/bigdecimal/commit/69d0588a3b
2022-11-13[ruby/bigdecimal] Tweak check_rounding_mode_optionKenta Murata
https://github.com/ruby/bigdecimal/commit/e1c6c9be25
2022-11-13[ruby/bigdecimal] Rewrite check_rounding_mode functionKenta Murata
Use table-lookup algorithm instead of consecutive if-statements. https://github.com/ruby/bigdecimal/commit/23eaff3ae5
2022-11-13[ruby/bigdecimal] [Doc] Fix the document of n_significant_digitsKenta Murata
https://github.com/ruby/bigdecimal/commit/91b72a9341
2022-11-13[ruby/bigdecimal] Make GetVpValue inlineKenta Murata
https://github.com/ruby/bigdecimal/commit/1b642e2e59
2022-11-13[ruby/bigdecimal] Make BigDecimal_double_fig inlineKenta Murata
https://github.com/ruby/bigdecimal/commit/4ecf04da7a
2022-11-12Migrate our resolver engine to PubGrubHiroshi SHIBATA
https://github.com/rubygems/rubygems/pull/5960 Co-authored-by: David Rodríguez <deivid.rodriguez@riseup.net>
2022-11-11[ruby/irb] Simplify info command's testsStan Lo
(https://github.com/ruby/irb/pull/440) https://github.com/ruby/irb/commit/5942949226
2022-11-11[ruby/net-http] Update lib/net/http.rbBurdette Lamar
https://github.com/ruby/net-http/commit/16d042fad6 Co-authored-by: Peter Zhu <peter@peterzhu.ca>
2022-11-11[ruby/net-http] Prettify class hierarchies in Net::HTTPBurdetteLamar
https://github.com/ruby/net-http/commit/4a5732e210
2022-11-11YJIT: Fix staying in invalidated code after proc callsAlan Wu
Previously, there is no instruction boundary patch point after the call to a non-leaf C function we generate for OPTIMIZED_METHOD_TYPE_CALL. This meant that if code GC is triggered while inside the C function, we would keep running invalidated code when we return from the C function. This had the effect of running stale branch stubs, jumping to bad code, etc. Use jit_prepare_routine_call() to make sure we exit from the invalidated region as soon as possible after the C call in case of invalidation. Notes: Merged: https://github.com/ruby/ruby/pull/6711
2022-11-11Enable only master-branchHiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/6716
2022-11-11Test with topic-branchHiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/6716
2022-11-11Use secrets.SCORECARD_READ_TOKENHiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/6716
2022-11-11Try to use ossf/scorecardsHiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/6716
2022-11-11Merge RubyGems/Bundler master from ee2f8398324af4bc1b95f7565ce2fda98126e026v3_2_0_preview3Hiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/6715
2022-11-11[rubygems/rubygems] Store last check even when upgrade is not available and ↵Josef Šimánek
fix test. https://github.com/rubygems/rubygems/commit/bcffc2b0a5 Notes: Merged: https://github.com/ruby/ruby/pull/6715
2022-11-11[rubygems/rubygems] Use file in XDG_STATE_HOME directory to store last ↵Josef Šimánek
update check timestamp. https://github.com/rubygems/rubygems/commit/0fbc4ace8a Notes: Merged: https://github.com/ruby/ruby/pull/6715
2022-11-11[rubygems/rubygems] Add 'call for update' to RubyGems install command.Josef Šimánek
https://github.com/rubygems/rubygems/commit/05811f8248 Notes: Merged: https://github.com/ruby/ruby/pull/6715
2022-11-11[rubygems/rubygems] github source should default to secure protocolJason Karns
Bundler 2 switched to secure https here https://github.com/rubygems/rubygems/commit/c2e81f8ff63613871cc8b52653c5e176f8dafde3 Insecure protocols should be avoided to prevent MITM attacks. https://github.com/rubygems/rubygems/commit/758413364a Notes: Merged: https://github.com/ruby/ruby/pull/6715
2022-11-11Allow a float error for Regexp.timeoutYusuke Endoh
The tests failed on windows https://github.com/ruby/ruby/actions/runs/3440997073/jobs/5740085169#step:18:62 ``` 1) Failure: TestRegexp#test_s_timeout [D:/a/ruby/ruby/src/test/ruby/test_regexp.rb:1586]: <0.30000000000000004> expected but was <0.3>. 2) Failure: TestRegexp#test_timeout_shorter_than_global [D:/a/ruby/ruby/src/test/ruby/test_regexp.rb:1631]: <0.30000000000000004> expected but was <0.3>. ```
2022-11-11wasm/README.md: Add a note about the Ruby built for wasm. [ci skip]Jun Aruga
The Ruby built for wasm cannot be execute without a WebAssembly runtime. ``` $ ruby-wasm32-wasi/usr/local/bin/ruby -e 'puts "a"' bash: ruby-wasm32-wasi/usr/local/bin/ruby: cannot execute binary file: Exec format error ``` Because the Ruby's file type is different from the one built normally, that is the `/usr/local/ruby-3.2.0-preview2/bin/ruby` below. ``` $ file ruby-wasm32-wasi/usr/local/bin/ruby ruby-wasm32-wasi/usr/local/bin/ruby: WebAssembly (wasm) binary module version 0x1 (MVP) $ file /usr/local/ruby-3.2.0-preview2/bin/ruby /usr/local/ruby-3.2.0-preview2/bin/ruby: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=a37822085e285c0971159982e7642dda88cea606, for GNU/Linux 3.2.0, with debug_info, not stripped ``` Notes: Merged: https://github.com/ruby/ruby/pull/6707
2022-11-10[ruby/irb] Transform ls's --grep/-G option to keyword argsTakashi Kokubun
(https://github.com/ruby/irb/pull/437) * Transform ls's --grep/-G option to keyword args * Make --grep less flexible * Support -g instead of --grep * Suppress warnings from symbol aliases
2022-11-10[rubygems/rubygems] Update bundler/spec/bundler/shared_helpers_spec.rbYusuke Endoh
https://github.com/rubygems/rubygems/commit/8b1481ba77 Co-authored-by: Nobuyoshi Nakada <nobu@ruby-lang.org>
2022-11-10[rubygems/rubygems] Load "bundler/setup" in lib/rubygems.rbYusuke Endoh
Ruby interpreter loads some special gems at startup: did_you_mean, error_highlight, and syntax_suggest. These gems are loaded before `bundler/setup` is loaded by `RUBYOPT=-rbundler/setup`. So, the versions of the gems are not controllable by Gemfile. This change will `require "bundler/setup"` in rubygems.rb (i.e., before the special gems are loaded). Now `bundle exec` sets an environment variable `BUNDLER_SETUP`, and rubygems requires the variable if defined. See also: https://bugs.ruby-lang.org/issues/19089 https://github.com/rubygems/rubygems/commit/963cb65a2d
2022-11-11Run EnvUtil.apply_timeout_scale outside of assert_separatelyYusuke Endoh
It does not work well in assert_separately
2022-11-10[ruby/racc] Make racc test more flexible (for JRuby).Thomas E. Enebo
JRuby uses these same files for testing racc. The existing logic will not find 'racc' in a JRuby project checkout. This change allows it to work by just assuming 'ruby -S racc' when running tests. This will not change C Ruby's detection when setting up tests (since earlier checks will find racc). https://github.com/ruby/racc/commit/b74ce5e018
2022-11-10YJIT: Invalidate JIT code only for ISEQ_TRACE_EVENTS (#6695)Takashi Kokubun
Notes: Merged-By: maximecb <maximecb@ruby-lang.org>
2022-11-10Define YJIT_STATS on --enable-yjit=stats (#6710)Takashi Kokubun
Notes: Merged-By: k0kubun <takashikkbn@gmail.com>
2022-11-10Extract `rb_shape_get_parent` helperJemma Issroff
Extract an `rb_shape_get_parent` method instead of continually calling `rb_shape_get_shape_by_id(shape->parent_id)` Notes: Merged: https://github.com/ruby/ruby/pull/6708
2022-11-10Remove inconsistencyTakashi Kokubun
I meant they should be also fixed in https://github.com/ruby/ruby/pull/6694#discussion_r1019445575
2022-11-10Enable --yjit-stats for release builds (#6694)Jimmy Miller
* Enable --yjit-stats for release builds In order for people in the real world to report information about how their application runs with YJIT, we want to expose stats without requiring rebuilding ruby. We can do this without overhead, with the exception of count ratio in yjit, since this relies on the interpreter also counting instructions. This change exposes those stats, while not showing ratio in yjit if we are not in a stats build. * Update yjit.rb Co-authored-by: Takashi Kokubun <takashikkbn@gmail.com> Co-authored-by: Maxime Chevalier-Boisvert <maximechevalierb@gmail.com> Notes: Merged-By: maximecb <maximecb@ruby-lang.org>
generated by cgit v1.2.3 (git 2.25.1) at 2026-01-21 00:24:50 +0000