summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* [rubygems/rubygems] util/rubocop -A --only Lint/RescueExceptionHiroshi SHIBATA2023-03-239-11/+11
| | | | https://github.com/rubygems/rubygems/commit/e8a5db50af
* [rubygems/rubygems] util/rubocop -A --only Lint/EmptyExpressionHiroshi SHIBATA2023-03-231-1/+1
| | | | | | Thread.report_on_exception is always defined after Ruby 2.4 or later. https://github.com/rubygems/rubygems/commit/274da54f38
* [rubygems/rubygems] util/rubocop -A --only Lint/DuplicateCaseConditionHiroshi SHIBATA2023-03-231-2/+0
| | | | https://github.com/rubygems/rubygems/commit/df2b192e47
* core_assertions.rb: Raise `Timeout::Error` explicitlyNobuyoshi Nakada2023-03-231-1/+1
| | | | So that `assert_raise` inside the block works.
* `Array#first` and `Array#last` in RubyKoichi Sasada2023-03-232-17/+56
|
* `vm_call_single_noarg_inline_builtin`Koichi Sasada2023-03-238-15/+114
| | | | | | | | If the iseq only contains `opt_invokebuiltin_delegate_leave` insn and the builtin-function (bf) is inline-able, the caller doesn't need to build a method frame. `vm_call_single_noarg_inline_builtin` is fast path for such cases.
* should not restore builtin_inline_indexKoichi Sasada2023-03-231-3/+0
| | | | | | | | `builtin_inline_index` is restored because THEN clause on `Primitive.mandatory_only?` was compiled twice. However, f29c9d6d36 skips to compile THEN clause so we don't need to restore `builtin_inline_index`.
* Bump github/codeql-action from 2.2.7 to 2.2.8dependabot[bot]2023-03-232-5/+5
| | | | | | | | | | | | | | | Bumps [github/codeql-action](https://github.com/github/codeql-action) from 2.2.7 to 2.2.8. - [Release notes](https://github.com/github/codeql-action/releases) - [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md) - [Commits](https://github.com/github/codeql-action/compare/168b99b3c22180941ae7dbdd5f5c9678ede476ba...67a35a08586135a9573f4327e904ecbf517a882d) --- updated-dependencies: - dependency-name: github/codeql-action dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
* Suppress a compiler warning on GCC in process.cPeter Zhu2023-03-221-0/+8
| | | | | | | rb_pid_t is 32 bits on some platforms, which will cause a warning on GCC due to POSFIXABLE always returning true. include/ruby/internal/arithmetic/fixnum.h:43:31: warning: comparison is always true due to limited range of data type [-Wtype-limits]
* [rubygems/rubygems] Use indented heredocNobuyoshi Nakada2023-03-229-20/+20
| | | | https://github.com/rubygems/rubygems/commit/085d2776d8
* Lazily allocate id tables for childrenAaron Patterson2023-03-222-22/+92
| | | | | | | | | | This patch lazily allocates id tables for shape children. If a shape has only one single child, it tags the child with a bit. When we read children, if the id table has the bit set, we know it's a single child. If we need to add more children, then we create a new table and evacuate the child to the new table. Co-Authored-By: Matt Valentine-House <matt@eightbitraptor.com>
* pull child allocation in to a different functionAaron Patterson2023-03-221-17/+25
|
* combine allocation functionsAaron Patterson2023-03-221-13/+6
|
* Make shape functions staticAaron Patterson2023-03-222-46/+41
| | | | | These functions don't need to be in the header file, we can declare them as static.
* Fix shape allocation limitsAaron Patterson2023-03-223-4/+5
| | | | | | | | | | We can only allocate enough shapes to fit in the shape buffer. MAX_SHAPE_ID was based on the theoretical maximum number of shapes we could have, not on the amount of memory we can actually consume. This commit changes the MAX_SHAPE_ID to be based on the amount of memory we're allowed to consume. Co-Authored-By: Jemma Issroff <jemmaissroff@gmail.com>
* core_assertions.rb: Fix backward compatibility with pre 2.7Nobuyoshi Nakada2023-03-221-1/+1
|
* [DOC] Update comment of assert_pattern_listNobuyoshi Nakada2023-03-221-2/+2
| | | | `pattern_list` may contain string since d903e7672637.
* [rubygems/rubygems] @orig_RUBY_ENGINE is always provided nowHiroshi SHIBATA2023-03-221-2/+1
| | | | https://github.com/rubygems/rubygems/commit/c5e8ad4823
* [rubygems/rubygems] Fix test failure with missing RUBY_REVISION constantsHiroshi SHIBATA2023-03-221-16/+1
| | | | https://github.com/rubygems/rubygems/commit/c5b80945c6
* [rubygems/rubygems] ditto: RUBY_ENGINE_VERSIONHiroshi SHIBATA2023-03-221-4/+4
| | | | https://github.com/rubygems/rubygems/commit/dc82ebeac6
* [rubygems/rubygems] RUBY_REVISION is also provided by supported platformsHiroshi SHIBATA2023-03-223-8/+8
| | | | https://github.com/rubygems/rubygems/commit/71a237aeec
* [rubygems/rubygems] RUBY_DESCRIPTION is always provided by supported platformsHiroshi SHIBATA2023-03-221-1/+1
| | | | https://github.com/rubygems/rubygems/commit/8a7028bc7e
* [rubygems/rubygems] FixupHiroshi SHIBATA2023-03-221-1/+1
| | | | | | https://github.com/rubygems/rubygems/pull/6486 https://github.com/rubygems/rubygems/commit/ad50221acf
* core_assertions.rb: Refine `assert_linear_performance`Nobuyoshi Nakada2023-03-221-1/+1
| | | | | * Calculate each timeout from the ratio of each factor to the first factor.
* Should not reach end of non-void functionNobuyoshi Nakada2023-03-221-6/+2
|
* Fixup 43d20596b8fefadc309348448352bf13615129c6Hiroshi SHIBATA2023-03-221-1/+2
|
* [rubygems/rubygems] Remove reference to `pry` gem from generated ↵Justin Searls2023-03-221-4/+0
| | | | | | `bin/console` file This is just a suggestion, but since recent versions of Ruby have shipped with a `binding.irb` that provides almost all of the features that `pry` pioneered, it may be time to remove this suggestion in the name of simplicity and not confusing newer developers who aren't familiar with what to use.
* Relax timeout limit for FreeBSDHiroshi SHIBATA2023-03-221-1/+1
| | | | | * http://rubyci.s3.amazonaws.com/freebsd12/ruby-master/log/20230322T063002Z.fail.html.gz * http://rubyci.s3.amazonaws.com/freebsd13/ruby-master/log/20230322T063002Z.fail.html.gz
* Added assertion values for Amazon Linux 2023Hiroshi SHIBATA2023-03-221-3/+5
|
* RJIT: Update bindingTakashi Kokubun2023-03-211-1/+2
|
* RJIT: Follow a recent CALLER_SETUP_ARG changeTakashi Kokubun2023-03-212-6/+10
|
* RJIT: Split has_rest_or_post exit reasonsTakashi Kokubun2023-03-213-7/+7
|
* [rubygems/rubygems] Bump rb-sysdependabot[bot]2023-03-222-7/+8
| | | | | | | | | | | | | | | Bumps [rb-sys](https://github.com/oxidize-rb/rb-sys) from 0.9.67 to 0.9.68. - [Release notes](https://github.com/oxidize-rb/rb-sys/releases) - [Commits](https://github.com/oxidize-rb/rb-sys/compare/v0.9.67...v0.9.68) --- updated-dependencies: - dependency-name: rb-sys dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
* YJIT: Fix deadlock in tests due to pipe capacityAlan Wu2023-03-211-2/+13
| | | | | | | | | | | | Previously, when there is enough stats that the child process fills up the pipe capacity, the child process would block, with the parent process waiting forever as no one is reading to clear up the pipe. The test timed out in these situations. Use a separate thread in the parent to read from the pipe to unblock the child in these situation. EnvUtil also does this for handling stdout and stderr. I had the test suite deadlock on a Linux VM.
* YJIT: Fix large ISeq rejection (#7576)Alan Wu2023-03-213-3/+30
| | | | | | | | | | | | We crashed in some edge cases due to the recent change to not compile encoded iseqs that are larger than `u16::MAX`. - Match the C signature of rb_yjit_constant_ic_update() and clamp down to `IseqIdx` size - Return failure instead of panicking with `unwrap()` in codegen when the iseq is too large Co-authored-by: Maxime Chevalier-Boisvert <maxime.chevalierboisvert@shopify.com> Co-authored-by: Noah Gibbs <noah.gibbs@shopify.com>
* YJIT: Fix incorrect exit in splat (#7575)Jimmy Miller2023-03-212-1/+16
| | | | | | | So by itself, this shouldn't have been a correctness issue, but we also pop the stack for block_args. Doing stack manipulation like that and then side-exiting causes issues. So, while this fixes the immediate failure, we have a bigger issue with block_args popping and then exiting that we need to deal with.
* [ruby/erb] [DOC] Use indented heredocNobuyoshi Nakada2023-03-211-2/+2
| | | | https://github.com/ruby/erb/commit/8ba8bb7acf
* Revert "YJIT: Rest and block_arg support (#7557)"Peter Zhu2023-03-213-24/+9
| | | | | | | | | | | | | | | | | | | | | | | This reverts commit 5d0a1ffafa61da04dbda38a5cb5565bcb8032a78. This commit is causing sequel in yjit-bench to raise with this stack trace: ``` sequel-5.64.0/lib/sequel/dataset/sql.rb:266:in `literal': wrong argument type Array (expected Proc) (TypeError) from sequel-5.64.0/lib/sequel/database/misc.rb:269:in `literal' from sequel-5.64.0/lib/sequel/adapters/shared/sqlite.rb:314:in `column_definition_default_sql' from sequel-5.64.0/lib/sequel/database/schema_methods.rb:564:in `block in column_definition_sql' from sequel-5.64.0/lib/sequel/database/schema_methods.rb:564:in `each' from sequel-5.64.0/lib/sequel/database/schema_methods.rb:564:in `column_definition_sql' from sequel-5.64.0/lib/sequel/database/schema_methods.rb:634:in `block in column_list_sql' from sequel-5.64.0/lib/sequel/database/schema_methods.rb:634:in `map' from sequel-5.64.0/lib/sequel/database/schema_methods.rb:634:in `column_list_sql' from sequel-5.64.0/lib/sequel/database/schema_methods.rb:753:in `create_table_sql' from sequel-5.64.0/lib/sequel/adapters/shared/sqlite.rb:348:in `create_table_sql' from sequel-5.64.0/lib/sequel/database/schema_methods.rb:702:in `create_table_from_generator' from sequel-5.64.0/lib/sequel/database/schema_methods.rb:203:in `create_table' from benchmarks/sequel/benchmark.rb:19:in `<main>' ```
* [ruby/reline] Add key bindings for PgUp and PgDnPhillip Hellewell2023-03-212-0/+16
| | | | | | | | | | | | | (https://github.com/ruby/reline/pull/509) * Add key bindings for PgUp, PgDn * Match behavior of readline 8.2 In the latest readline (8.2), page-up and page-down are bound to history-search-backward and history-search-forward by default. We would like reline to have the same default behavior.
* Use indented heredocNobuyoshi Nakada2023-03-211-2/+2
|
* Update dln.c to fix error output from `dln_open()`drew-wells2023-03-211-0/+6
| | | | | `libruby_name` gets trashed by `dlclose(handle)`, so output the "linked to incompatible ... " error before calling `dlclose(handle)`.
* [ci skip] Move rb_id2str into new LLDB formatMatt Valentine-House2023-03-212-1/+50
|
* RJIT: Fix invokesuperTakashi Kokubun2023-03-212-7/+5
|
* Bump ruby/setup-ruby from 1.144.1 to 1.144.2dependabot[bot]2023-03-214-4/+4
| | | | | | | | | | | | | | Bumps [ruby/setup-ruby](https://github.com/ruby/setup-ruby) from 1.144.1 to 1.144.2. - [Release notes](https://github.com/ruby/setup-ruby/releases) - [Commits](https://github.com/ruby/setup-ruby/compare/e6689b4deb1cb2062ea45315001f687c0b52111b...ec02537da5712d66d4d50a0f33b7eb52773b5ed1) --- updated-dependencies: - dependency-name: ruby/setup-ruby dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
* Use an st table for "too complex" objectsAaron Patterson2023-03-209-46/+74
| | | | | | | | | | st tables will maintain insertion order so we can marshal dump / load objects with instance variables in the same order they were set on that particular instance [ruby-core:112926] [Bug #19535] Co-Authored-By: Jemma Issroff <jemmaissroff@gmail.com>
* YJIT: Make dev_nodebug closer to dev (#7570)Takashi Kokubun2023-03-202-3/+5
|
* Update yjit.mdMaxime Chevalier-Boisvert2023-03-201-1/+2
| | | Document `make yjit-smoke-test`
* YJIT: tag output type as UnknownHeap in `toregexp` (#7562)Maxime Chevalier-Boisvert2023-03-201-1/+1
|
* Mark cached pid if necessaryNobuyoshi Nakada2023-03-201-2/+7
|
* Fix the macro for conditionNobuyoshi Nakada2023-03-201-1/+1
|
View Lorry Controller Status