summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Define BOOTSTRAPRUBY from HAVE_BASERUBYNobuyoshi Nakada2022-09-074-12/+10
|
* Fix typoTakashi Kokubun2022-09-071-1/+1
| | | | I meant the other one. Otherwise this option doesn't make sense.
* Adjust pch_status for --mjit=pauseTakashi Kokubun2022-09-061-1/+2
| | | | to let mjit_add_iseq_to_process work
* Skip early mjit_add_iseq_to_process on --mjit=pauseTakashi Kokubun2022-09-061-1/+1
|
* Now Psych uses the proleptic Gregorian calendarNobuyoshi Nakada2022-09-071-4/+0
|
* Skip calling check_unit_queue with mjit_opts.customTakashi Kokubun2022-09-061-0/+1
| | | | fixing the behavior of b726c06e7eeafff52e368179dbe79a11b1aff975
* Use BOOTSTRAPRUBY_COMMAND instead of fake.rb directlyNobuyoshi Nakada2022-09-071-1/+1
|
* Ensure BASERUBY when cross-compilingNobuyoshi Nakada2022-09-072-0/+9
|
* [ruby/psych] Bump snakeyaml from 1.28 to 1.31Chad Wilson2022-09-071-1/+1
| | | | | | Resolves CVE-2022-25857, among other fixes. https://github.com/ruby/psych/commit/918cd25d37
* [ruby/psych] Dump Date/DateTime as proleptic Gregorian date as well as TimeNobuyoshi Nakada2022-09-074-10/+32
| | | | | | Fix ruby/psych#572 https://github.com/ruby/psych/commit/92304269bc
* fixup 8cd6f2a0872e74c6cc089d2a4f8140483080c67aHiroshi SHIBATA2022-09-071-3/+1
| | | | we should handle ensure block when omit this test
* Add another method for debuggingTakashi Kokubun2022-09-071-0/+6
|
* [rubygems/rubygems] Fix: Gem info bug with version flagAntonio Paulino2022-09-072-2/+28
| | | | https://github.com/rubygems/rubygems/commit/e4cee1f975
* Drop an unused method for debuggingTakashi Kokubun2022-09-071-7/+4
| | | | and add another useful one instead.
* * 2022-09-07 [ci skip]git2022-09-071-1/+1
|
* Exit status macros need sys/wait.h on FreeBSDNobuyoshi Nakada2022-09-071-0/+4
|
* [rubygems/rubygems] Fix `set` not being found when running specs on dev rubiesDavid Rodríguez2022-09-061-0/+3
| | | | https://github.com/rubygems/rubygems/commit/c5b2960388
* [rubygems/rubygems] Add `syntax_suggest` to exemption list in setup specsDavid Rodríguez2022-09-061-0/+1
| | | | https://github.com/rubygems/rubygems/commit/f9a51e4380
* omit random failure in bootstraptest with freebsdHiroshi SHIBATA2022-09-061-0/+1
| | | | http://rubyci.s3.amazonaws.com/freebsd13/ruby-master/log/20220902T063002Z.fail.html.gz
* omit random failure tests with FreeBSDHiroshi SHIBATA2022-09-062-0/+3
| | | | | http://rubyci.s3.amazonaws.com/freebsd13/ruby-master/log/20220906T043002Z.fail.html.gz http://rubyci.s3.amazonaws.com/freebsd13/ruby-master/log/20220905T103002Z.fail.html.gz
* Fix typoTakashi Kokubun2022-09-061-1/+1
|
* Update c_32.rbTakashi Kokubun2022-09-061-2/+2
|
* Run mjit-bindgen againTakashi Kokubun2022-09-062-2/+6
| | | | | | I'm thinking about Ruby builtin code instead of doing this. It'll be hopefully more portable and easier because the same C code could handle both 32bit and 64bit.
* Allow hooking a different method after --mjit=pauseTakashi Kokubun2022-09-062-10/+39
| | | | | The interface is similar to RubyVM::ISeq.translate; it's used if defined. Same as --mjit=pause, this is an undocumented feature for MJIT experiments.
* Cache RubyVM::MJIT constantsTakashi Kokubun2022-09-062-8/+11
| | | | for performance
* Add an option to lazily boot MJIT for experimentsTakashi Kokubun2022-09-062-6/+21
| | | | | | You may use `RUBYOPT=--mjit=pause irb` to play with RubyVM::MJIT::C, control the boot timing of MJIT, or customize the implementation while paused. It's an undocumented feature for such experiments.
* Do not fork the process on --mjit-waitTakashi Kokubun2022-09-064-24/+26
| | | | | fork is for parallel compilation, but --mjit-wait cancels it. It's more useful to not fork it for binding.irb, debugging, etc.
* Skip test_redefinition_mismatch on trunk-mjit for nowTakashi Kokubun2022-09-061-0/+1
| | | | | | Investigating: http://ci.rvm.jp/logfiles/brlog.trunk-mjit.20220906-025646 which is not immediately reproducible on my laptop.
* Update default gems list at 2657d8efb9d38761c1e09f54fadea4 [ci skip]git2022-09-061-1/+1
|
* [ruby/set] Bump version to 1.0.3Hiroshi SHIBATA2022-09-061-1/+1
| | | | https://github.com/ruby/set/commit/e2419f2d30
* Deal with MJIT_FORCE_ENABLE minirubyTakashi Kokubun2022-09-051-0/+9
| | | | http://ci.rvm.jp/results/trunk-mjit@phosphorus-docker/4225469
* * 2022-09-06 [ci skip]git2022-09-061-1/+1
|
* Workaround unused variable warning by builtinTakashi Kokubun2022-09-051-30/+28
| | | | | | | | | | | | | | | | | | | | | | ``` <internal:mjit_compiler>:43: warning: assigned but unused variable - iseq_addr <internal:mjit_compiler>:48: warning: assigned but unused variable - ci_addr <internal:mjit_compiler>:53: warning: assigned but unused variable - ci_addr <internal:mjit_compiler>:58: warning: assigned but unused variable - ci_addr <internal:mjit_compiler>:63: warning: assigned but unused variable - ci_addr <internal:mjit_compiler>:64: warning: assigned but unused variable - cc_addr <internal:mjit_compiler>:65: warning: assigned but unused variable - iseq_addr <internal:mjit_compiler>:75: warning: assigned but unused variable - operands_addr <internal:mjit_compiler>:80: warning: assigned but unused variable - compiled_body_addr <internal:mjit_compiler>:81: warning: assigned but unused variable - captured_body_addr <internal:mjit_compiler>:87: warning: assigned but unused variable - body_addr <internal:mjit_compiler>:88: warning: assigned but unused variable - is_entries_addr <internal:mjit_compiler>:100: warning: assigned but unused variable - opes_addr <internal:mjit_compiler>:110: warning: assigned but unused variable - cc_entries_addr ``` It's clearly a false positive. Until we fix builtin itself, I'd like to suppress this.
* [rubygems/rubygems] Remove no longer needed `fiddle` hacksDavid Rodríguez2022-09-054-13/+0
| | | | | | | RubyInstaller has released patch versions backporting their changes to not load `fiddle` on boot, so all these are no longer necessary. https://github.com/rubygems/rubygems/commit/05a307deb2
* [DOC] [Bug #17120] Fix match-reset `\K`Nobuyoshi Nakada2022-09-051-5/+9
|
* Update default gems list at 113581d288496f8f3e60851b76b751 [ci skip]git2022-09-051-0/+1
|
* [ruby/set] Set version to 1.0.3.dev for fixing rubygems/bundler testsHiroshi SHIBATA2022-09-051-1/+1
| | | | https://github.com/ruby/set/commit/40dda15d7f
* Stop testing MJIT on s390xTakashi Kokubun2022-09-052-16/+10
| | | | | It didn't work either. http://rubyci.s3.amazonaws.com/s390x/ruby-master/log/20220905T080003Z.fail.html.gz
* Update MJIT doc about bindgen and platforms [ci skip]Takashi Kokubun2022-09-052-16/+78
|
* Drop Solaris support for MJITTakashi Kokubun2022-09-051-1/+1
| | | | | | | | | | | I tried to debug: http://rubyci.s3.amazonaws.com/solaris10-gcc/ruby-master/log/20220905T070005Z.fail.html.gz but I don't have sudo privilege to install dependencies such as xz on that machine. Thus I can't extract a prebuilt libclang binary. Anyway, if we find out ABI is different from x86_64 / aarch64, we'd like to have sparc CI associated to GitHub to run `make mjit-bindgen`, but we can't. Supporting this could be too hard, so I'm leaving it for now.
* Add mjit-bindgen workflow (#6327)Takashi Kokubun2022-09-054-28/+145
|
* Fix warnings from private_constantTakashi Kokubun2022-09-051-1/+1
| | | | `private_constant *constants` seems to be warned for some reason
* Automatically detect 64bit platformsTakashi Kokubun2022-09-041-2/+2
|
* s390x seems like a 64bit architectureTakashi Kokubun2022-09-041-1/+1
|
* Merge ↵Hiroshi SHIBATA2022-09-0569-831/+499
| | | | https://github.com/rubygems/rubygems/commit/16c3535413afebcdbab7582c6017c27b5da8a8dc
* Ruby MJIT (#6028)Takashi Kokubun2022-09-0430-1183/+3070
|
* Attempt to fix test-bundlerTakashi Kokubun2022-09-041-1/+1
| | | | | | f7cf641469161c3770b58f79e08e312512212aa8 broke spec/bundler/install/gems/resolving_spec.rb:356. This line seems to impact that test, so I slightly modified the implementation for that spec's case.
* Debugging snapshot [ci skip]Nobuyoshi Nakada2022-09-052-3/+4
|
* [rubygems/rubygems] Feature: `bundle add` supports `--path` optionMike Dalessio2022-09-056-4/+23
| | | | https://github.com/rubygems/rubygems/commit/32bee01fbe
* [rubygems/rubygems] Fix resolution hanging on musl platformsDavid Rodríguez2022-09-054-9/+35
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | After recent musl support was added, Bundler started hanging in musl platforms. I identified the issue where valid candidates were being filtered out because their platform was specified as a string, and thus `Gem::Platform.match_spec?` which under the hood ends up calling `Gem::Platform#===` would return `nil`, because it does not support comparing platforms to strings. In particular, `Bundler::EndpointSpecification`'s platform coming from the API was not instantiated as a `Gem::Platform`, hence the issue. Also, this spec surfaced another issue where a bug corrected in `Gem::Platform#match_platforms` had not been yet backported to Bundler. So this commit also backports that to get the spec green across RubyGems versions. Finally, the fix in `Bundler::EndpointSpecification` made a realworld spec start failing. This spec was faking out `rails-4.2.7.1` requirement on Bundler in the `Gemfile.lock` file to be `>= 1.17, < 3` when the real requirement is `>= 1.17, < 2`. Due to the bug in `Bundler::EndpointSpecification`, the real requirement provided by the compact index API (recorded with VCR) was being ignored, and the `Gemfile.lock` fake requirement was being used, which made the spec pass. This is all expected, and to fix the issue I changed the spec to be really realworld and don't fake any Bundler requirements. https://github.com/rubygems/rubygems/commit/faf4ef46bc
View Lorry Controller Status