aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* reorder bitmap clearing.Koichi Sasada2019-05-301-2/+2
|
* move pinned_bits[] position in struct heap_page.Koichi Sasada2019-05-301-2/+3
| | | | | pinned_bits are not used frequently (only GC.compact use it) so move it at the end of struct heap_page.
* introduce `during_compacting` flag.Koichi Sasada2019-05-301-13/+23
| | | | | Usually PINNED_BITS are not needed (only for GC.compact need it) so skip updating PINNED_BITS if the marking is not by GC.compact.
* Do not rely on IRB.conf[:MAIN_CONTEXT] before initializeTakashi Kokubun2019-05-301-2/+5
| | | | so that we can colorize binding.irb source lines.
* Check the end token of heredoc correctlyaycabta2019-05-301-0/+2
|
* Calculate vertical position correctly when rerendering all linesaycabta2019-05-301-1/+2
|
* Fix broken rendering when the last line is auto-wrappedaycabta2019-05-301-5/+5
|
* Rerender following lines when line number increasedaycabta2019-05-301-1/+1
|
* Clear remaining lines when line number decreasedaycabta2019-05-301-6/+24
|
* parse.y: continue after heredoc errorNobuyoshi Nakada2019-05-302-2/+16
| | | | | * parse.y: continue parsing the rest of the here-document starting line, after the terminator was not found.
* Fix the auto-wrap behabior that was too buggyaycabta2019-05-301-23/+32
|
* Use Regexp#match instead of #match for 1.9 BASERUBY supportJeremy Evans2019-05-291-1/+1
|
* Revert "Fix building with 1.8 BASERUBY"Jeremy Evans2019-05-294-8/+7
| | | | | | | | | This reverts commit 05bc14d81a1d7f6af826a92371aeff0c3fb2a67e. We have decided that the cost of reintroducing support for 1.8 BASERUBY outweighs the benefit. If you are still using 1.8 and want to build master/trunk, build and install the latest release, and use that as BASERUBY.
* * 2019-05-30git2019-05-301-1/+1
|
* Do not use rb_iseq_path() while moving ISeq pointersTakashi Kokubun2019-05-301-26/+14
| | | | | | | | in GC.compact. While `in_jit` is false, GC.compact is allowed to run and it may be moving ISeq-related pointers. So calling rb_iseq_path() when `in_jit` is true is illegal.
* Colorize errors moreNobuyoshi Nakada2019-05-292-6/+16
| | | | | * lib/irb/color.rb (IRB::Color.colorize_code): colorize `compile_error` part as same as `on_parse_error`.
* Get rid of nested string interpolationsNobuyoshi Nakada2019-05-291-1/+2
| | | | | * lib/irb/color.rb (IRB::Color.colorize): get rid of nesting string interpolations not to confuse ruby-mode.el
* parse.y: fix state after ivar/cvarNobuyoshi Nakada2019-05-292-2/+21
| | | | | * parse.y (parse_atmark): return EXPR_END or EXPR_ENDFN, depending on the previous state, even incomplete names consistently.
* Revert "Use "require" just for essential"aycabta2019-05-291-1/+1
| | | | This reverts commit ab7a6e1a1651d82d327d155b78a8e3af1d976707.
* Use "require" just for essentialaycabta2019-05-291-1/+1
| | | | | The 559dca509d2a98584b09c7d9a6d74749ce793ad7 contains an excess range in using "require".
* Use reversed get_screen_size correctly on Windowsaycabta2019-05-291-2/+2
|
* ripper: Ripper::Lexer#scanNobuyoshi Nakada2019-05-292-18/+39
| | | | | | * ext/ripper/lib/ripper/lexer.rb (Ripper::Lexer#scan): parses the code and returns the result elements including errors. [EXPERIMENTAL]
* Never make a method call from MJIT workerTakashi Kokubun2019-05-291-6/+9
| | | | | | by showing line number only when it's Fixnum. When it's not Fixnum, we need to call a method to know the line number.
* Do not call FIX2INT while GC.compact may be runningTakashi Kokubun2019-05-291-6/+6
| | | | | because FIX2INT might crash by moving method entry pointer: http://ci.rvm.jp/results/trunk-mjit@silicon-docker/2063412
* .travis.yml: Minor reorder for shorteningTakashi Kokubun2019-05-291-1/+1
|
* Convert Enumerator to Array for Ruby 1.9.3Takashi Kokubun2019-05-291-1/+1
| | | | | String#lines seems to return Enumerator in Ruby 1.9.3, and it does not respond to #delete_if https://travis-ci.org/ruby/ruby/jobs/538559919
* Skip spec broken since a66bc2c01194a9c017c874a30db5b3b6bd95e966Takashi Kokubun2019-05-291-23/+27
| | | | This has not worked since the merge https://travis-ci.org/ruby/ruby/jobs/538438184
* Colorize compile_error as same as on_parse_errorNobuyoshi Nakada2019-05-292-3/+4
|
* parse.y: flush invalid charNobuyoshi Nakada2019-05-293-2/+14
|
* Fix shorten-64-to-32 warningNobuyoshi Nakada2019-05-291-1/+1
|
* Fix Possible Control flow issues (DEADCODE)Kazuhiro NISHIYAMA2019-05-292-6/+10
| | | | | Coverity Scan says `Execution cannot reach this statement: "poison_object(v);"`, so do nothing when `ptr` is always 0 without address_sanitizer.
* test/rubygems/test_gem_stream_ui.rb (test_ask_for_password): extend the timeoutYusuke Endoh2019-05-291-1/+1
| | | | | | for Solaris. https://rubyci.org/logs/rubyci.s3.amazonaws.com/unstable10s/ruby-master/log/20190528T191908Z.fail.html.gz
* Revert "Colorize error part more"Koichi Sasada2019-05-291-28/+11
| | | | This reverts commit c7f3c222c9b82736c993419daa6bfb643e5c0793.
* Colorize error part moreNobuyoshi Nakada2019-05-291-11/+28
| | | | Colorize `compile_error` parts as well as `on_parse_error` parts.
* Create empty revision.tmp if BASERUBY is not yesNobuyoshi Nakada2019-05-291-4/+3
|
* Remove extra items because Reline::HISTORY is a sized queueaycabta2019-05-292-2/+55
|
* Create empty revision.tmp if no BASERUBYNobuyoshi Nakada2019-05-291-1/+3
|
* appveyor.yml - update for msys2 - pdcurses, force toolchainMSP-Greg2019-05-291-2/+4
| | | | | | | Closes: https://github.com/ruby/ruby/pull/2208 Merging the PR for fixing AppVeyor msys2 failure related to GCC 9 like: https://ci.appveyor.com/project/ruby/ruby/builds/24877992/job/ned5k4k5rwxnld5j
* Revert 3b7862c8e88cd7838a53ec083ac5733386400956 causing various CI hangsTakashi Kokubun2019-05-294-51/+5
| | | | | | | | | | | | | | | | | | | | | and dependent commits c67934b1c3b40dda5f170b032423e520511c68dd and f0d1dc5cee87dfb023cb43a2db9bcdef5a8dee8f. RubyCI and ci.rvm.jp are almost dead by timeout since this commit. --- Revert "Skip a reline test hanging on Wercker since 3b7862c8e8" This reverts commit f0d1dc5cee87dfb023cb43a2db9bcdef5a8dee8f. Revert "Remove extra items because Reline::HISTORY is a sized queue" This reverts commit c67934b1c3b40dda5f170b032423e520511c68dd. Revert "Use existing instances for LineEditor and Config" This reverts commit 3b7862c8e88cd7838a53ec083ac5733386400956.
* Prevent MJIT compilation from running while movingTakashi Kokubun2019-05-291-0/+4
| | | | | | | | pointers. Instead of 4fe908c1643c3f355edd787bb651aefb53b996c0, just locking the MJIT worker may be fine for this case. And also we might have the same issue in all `gc_compact_after_gc` calls.
* Make tool/vcs.rb compliant to BASERUBYTakashi Kokubun2019-05-291-1/+2
| | | | | | People seem to consider BASERUBY is either 1.8 or 1.9 now. Since this file may be executed by BASERUBY from file2lastrev.rb, I think we should not rely on Ruby 2.0 in this file for now.
* Check the result of file2lastrev.rb if HAVE_BASERUBYTakashi Kokubun2019-05-291-2/+5
| | | | | | | | | | | | is yes. We ignored the failure status of file2lastrev.rb on 73da429c36c, but it was for an environment without BASERUBY. I think we should skip running file2lastrev.rb on HAVE_BASERUBY=no, and run it and check the status on HAVE_BASERUBY=yes. Otherwise we may have an ignored arbitrary error of file2lastrev.rb on HAVE_BASERUBY=yes environment.
* Skip a reline test hanging on Wercker since 3b7862c8e8Takashi Kokubun2019-05-291-0/+1
| | | | like https://app.wercker.com/ruby/ruby/runs/mjit-test1/5cedad11105780001c4e7001?step=5cedaf6b48fad200076fe77b
* Add TESTOPTS=-v for Wercker test-all --jit-waitTakashi Kokubun2019-05-291-1/+1
| | | | because it's hard to identify which test causes a hang for now.
* Use IO.copy_streamaycabta2019-05-291-3/+1
|
* Check RUBY_YES_I_AM_NOT_A_NORMAL_USER env to access RubyVM docaycabta2019-05-291-1/+1
|
* IRB never show RubyVM's docaycabta2019-05-292-1/+49
|
* Encode completed strings corecctlyaycabta2019-05-291-1/+1
|
* Test BASERUBY: Ruby 1.9.3 on TravisTakashi Kokubun2019-05-291-0/+9
| | | | | | | | | | | We have no clear assertion or check of BASERUBY requirement. I want to make the current situation more explicit. I'm NOT saying we should support Ruby 1.9.3 here, but I'm just checking the situation as per 05bc14d81a1d7f6af826a92371aeff0c3fb2a67e. FYI, at this moment Ruby 1.8.7 did not work with this Travis config, like: https://travis-ci.org/k0kubun/ruby/builds/538459100
* Update to ruby/spec@0c5c5c1Benoit Daloze2019-05-281-7/+3
|
generated by cgit v1.2.3 (git 2.39.1) at 2024-06-23 02:29:14 +0000