summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2019-11-18add casts.Koichi Sasada
add casts to avoid compile error. http://ci.rvm.jp/results/trunk_clang_39@silicon-docker/2402215
2019-11-18catch up last commit.Koichi Sasada
Array#pack uses `opt_invokebuiltin_delegate_leave` now.
2019-11-18vm_invoke_builtin_delegate with start index.Koichi Sasada
opt_invokebuiltin_delegate and opt_invokebuiltin_delegate_leave invokes builtin functions with same parameters of the method. This technique eliminate stack push operations. However, delegation parameters should be completely same as given parameters. (e.g. `def foo(a, b, c) __builtin_foo(a, b, c)` is okay, but __builtin_foo(b, c) is not allowed) This patch relaxes this restriction. ISeq has a local variables table which includes parameters. For example, the method defined as `def foo(a, b, c) x=y=nil`, then local variables table contains [a, b, c, x, y]. If calling builtin-function with arguments which are sub-array of the lvar table, use opt_invokebuiltin_delegate instruction with start index. For example, `__builtin_foo(b, c)`, `__builtin_bar(c, x, y)` is okay, and so on.
2019-11-18update deps.Koichi Sasada
https://travis-ci.org/ruby/ruby/jobs/613242256#L2205
2019-11-18* remove trailing spaces. [ci skip]git
2019-11-18Update NEWS for $SAFE/taint changesJeremy Evans
Notes: Merged: https://github.com/ruby/ruby/pull/2476
2019-11-18Remove mention of $SAFE and taint from doc [ci skip]Jeremy Evans
Notes: Merged: https://github.com/ruby/ruby/pull/2476
2019-11-18Deprecate rb_eval_cmd, add rb_eval_cmd_kwJeremy Evans
rb_eval_cmd takes a safe level, and now that $SAFE is deprecated, it should be deprecated as well. Replace with rb_eval_cmd_kw, which takes a keyword flag. Switch the two callers to this function. Notes: Merged: https://github.com/ruby/ruby/pull/2476
2019-11-18[ruby/strscan] Remove taint supportJeremy Evans
Ruby 2.7 deprecates taint and it no longer has an effect. The lack of taint support should not cause a problem in previous Ruby versions. Notes: Merged: https://github.com/ruby/ruby/pull/2476
2019-11-18[ruby/openssl] Remove taint supportJeremy Evans
Ruby 2.7 deprecates taint and it no longer has an effect. The lack of taint support should not cause a problem in previous Ruby versions. Notes: Merged: https://github.com/ruby/ruby/pull/2476
2019-11-18[ruby/io-console] Remove taint supportJeremy Evans
Ruby 2.7 deprecates taint and it no longer has an effect. The lack of taint support should not cause a problem in previous Ruby versions. Notes: Merged: https://github.com/ruby/ruby/pull/2476
2019-11-18[ruby/etc] Remove taint supportJeremy Evans
Ruby 2.7 deprecates taint and it no longer has an effect. The lack of taint support should not cause a problem in previous Ruby versions. Still untaint the tmpdir object on Ruby <2.7, as returning a tainted string there could cause problems. Notes: Merged: https://github.com/ruby/ruby/pull/2476
2019-11-18[ruby/rss] Only check taint on Ruby <2.7Jeremy Evans
Ruby 2.7 deprecates taint and it no longer has an effect. Notes: Merged: https://github.com/ruby/ruby/pull/2476
2019-11-18[ruby/rexml] Only taint on Ruby <2.7Jeremy Evans
Ruby 2.7 deprecates taint and it no longer has an effect. Notes: Merged: https://github.com/ruby/ruby/pull/2476
2019-11-18More fixes for $SAFE/taint post mergingJeremy Evans
Notes: Merged: https://github.com/ruby/ruby/pull/2476
2019-11-18Deprecate taint/trust and related methods, and make the methods no-opsJeremy Evans
This removes the related tests, and puts the related specs behind version guards. This affects all code in lib, including some libraries that may want to support older versions of Ruby. Notes: Merged: https://github.com/ruby/ruby/pull/2476
2019-11-18Warn on access/modify of $SAFE, and remove effects of modifying $SAFEJeremy Evans
This removes the security features added by $SAFE = 1, and warns for access or modification of $SAFE from Ruby-level, as well as warning when calling all public C functions related to $SAFE. This modifies some internal functions that took a safe level argument to no longer take the argument. rb_require_safe now warns, rb_require_string has been added as a version that takes a VALUE and does not warn. One public C function that still takes a safe level argument and that this doesn't warn for is rb_eval_cmd. We may want to consider adding an alternative method that does not take a safe level argument, and warn for rb_eval_cmd. Notes: Merged: https://github.com/ruby/ruby/pull/2476
2019-11-18* 2019-11-18 [ci skip]git
2019-11-18Remove unnecessary checkaycabta
2019-11-17[ruby/irb] Remove ruby-token.rb from spec.filesaycabta
https://github.com/ruby/irb/commit/0180dc74bc
2019-11-17[ruby/irb] Version 1.1.0.pre.4aycabta
https://github.com/ruby/irb/commit/4945d0e676
2019-11-17[ruby/reline] Version 0.0.5aycabta
https://github.com/ruby/reline/commit/d57c7ea252
2019-11-17* 2019-11-17 [ci skip]git
2019-11-17Fix typosKazuhiro NISHIYAMA
2019-11-15[ruby/reline] Restore left cursor key support on Unix like OSes...aycabta
https://github.com/ruby/reline/commit/98b72af751
2019-11-15Implement em_set_mark and em_exchange_markaycabta
2019-11-15Fix a typo [ci skip]Kazuhiro NISHIYAMA
2019-11-15* 2019-11-15 [ci skip]git
2019-11-15load prelude.rb by builtin features.Koichi Sasada
The script in prelude.rb was embed in MRI to load it (eval this script at everyboot). This commit change the loading process of prelude.rb. MRI doesn't eval a script, but load from compiled binary with builtin feature. So that Init_prelude() does not load `prelude.rb` now.
2019-11-14delete unused functions卜部昌平
Looking at the list of symbols inside of libruby-static.a, I found hundreds of functions that are defined, but used from nowhere. There can be reasons for each of them (e.g. some functions are specific to some platform, some are useful when debugging, etc). However it seems the functions deleted here exist for no reason. This changeset reduces the size of ruby binary from 26,671,456 bytes to 26,592,864 bytes on my machine. Notes: Merged: https://github.com/ruby/ruby/pull/2677
2019-11-14`#@1` is no longer an embedded variableNobuyoshi Nakada
2019-11-14Added default gems entry to NEWSHiroshi SHIBATA
2019-11-14Update RubyGems and Bundler entries on NEWSHiroshi SHIBATA
2019-11-14test/ruby/test_proc.rb: suppress "method redefined" warningsYusuke Endoh
2019-11-14move rb_vm_lvar_exposed() correctly.Koichi Sasada
rb_vm_lvar_exposed() is prepared for __builtin_inline!(), needed for mini_builtin.c and builtin.c. However, it's only on builtin.c. So move it to make it as a part of VM.
2019-11-13Suspend many fibers test on JIT for nowTakashi Kokubun
https://github.com/ruby/ruby/runs/301411717 No C backtrace information and this is hard to fix immediately. As CI doesn't provide helpful information, this should be debugged locally or at least have more logs there.
2019-11-13Make GitHub Actions notification more like TravisTakashi Kokubun
Build's sequential number is a link in Travis, and also YYYY-MM-DD-XX is a little hard to parse.
2019-11-14* 2019-11-14 [ci skip]git
2019-11-14try to remove vm_core.hKoichi Sasada
2019-11-13Use shallow-since instead of depthKazuhiro NISHIYAMA
commit number of today requires log since 0:00 UTC. So commits of 24 hours are enough. https://www.git-scm.com/docs/git-clone#Documentation/git-clone.txt---depthltdepthgt > Implies --single-branch unless --no-single-branch is given to fetch the histories near the tips of all branches. So I add `--single-branch` too. Notes: Merged: https://github.com/ruby/ruby/pull/2680
2019-11-13Add commit number of today to notification of mjit CI tooKazuhiro NISHIYAMA
Notes: Merged: https://github.com/ruby/ruby/pull/2679
2019-11-13Check more likely condition first [Feature #16335]Nobuyoshi Nakada
2019-11-12Skip tailcall test for MJITTakashi Kokubun
failing in https://github.com/ruby/ruby/runs/300579218
2019-11-12Fix MJIT test's Slack notificationTakashi Kokubun
2019-11-13Removed sync library from sync toolHiroshi SHIBATA
2019-11-13Add missing Makefile dependencies for the tool/insns2vm.rb scriptDylan Thacker-Smith
Notes: Merged: https://github.com/ruby/ruby/pull/2657
2019-11-13Avoid top-level search for nested constant reference from nil in defined?Dylan Thacker-Smith
Fixes [Bug #16332] Constant access was changed to no longer allow top-level constant access through `nil`, but `defined?` wasn't changed at the same time to stay consistent. Use a separate defined type to distinguish between a constant referenced from the current lexical scope and one referenced from another namespace. Notes: Merged: https://github.com/ruby/ruby/pull/2657
2019-11-13Suppress warnings except for when last evaluationaycabta
Co-authored-by: Kazuhiro NISHIYAMA <zn@mbf.nifty.com>
2019-11-12We're not using Azure Pipelines anymoreTakashi Kokubun
2019-11-13Update badges of GitHub ActionsKazuhiro NISHIYAMA