summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2020-04-18RUBY_SPECIAL_SHIFT and RUBY_FL_USHIFT are mandatory for rp in lldb_cruby.pyNobuyoshi Nakada
2020-04-18Super TestJIT#setup to skip unsupported envsTakashi Kokubun
Slightly simplifying 8d6aa06620b316904fd10d0cab1b85e07f2fbf67
2020-04-18Skip a too-unstable test on s390x-linuxTakashi Kokubun
In the last 26-ish hours, it has failed 5 times: https://travis-ci.org/github/ruby/ruby/jobs/676497718 https://travis-ci.org/github/ruby/ruby/jobs/676480295 https://travis-ci.org/github/ruby/ruby/jobs/676103216 https://travis-ci.org/github/ruby/ruby/jobs/676057967 https://travis-ci.org/github/ruby/ruby/jobs/676055113 and I don't think anybody has been working on it right now. To make CI result report of s390x-linux useful, let's skip it until the test is improved to be more stable.
2020-04-18test/ruby/test_jit_debug.rb: Skip unsupported platformsYusuke Endoh
2020-04-18power_assert repository is transferred to ruby/power_assertKazuki Tsujimoto
2020-04-17Remove invalid webhook configTakashi Kokubun
According to warnings on Travis, there's no such key. We handle this on webhook side anyway.
2020-04-18* 2020-04-18 [ci skip]git
2020-04-17Compilation error does not impact exit statusTakashi Kokubun
We failed to ignore https://ci.appveyor.com/project/ruby/ruby/builds/32245902/job/xcfxw67uexxysvni
2020-04-17Fix a typo [ci skip]Kazuhiro NISHIYAMA
2020-04-17NEWS.md: Mentioned the removal of NIL/TRUE/FALSE [ci skip]Nobuyoshi Nakada
2020-04-17Removed NIL/TRUE/FALSE from documents tooKazuhiro NISHIYAMA
This is follow up of 62554ca97812b454e78a0a9daf6e962ff7a2f589
2020-04-17Removed NIL/TRUE/FALSENobuyoshi Nakada
Deprerecated constants which had been warned since 2.4.
2020-04-17Rescue EPIPE in _reportNobuyoshi Nakada
Instead of letting callers rescue the error always.
2020-04-17Refactored rb_readwrite_syserr_failNobuyoshi Nakada
* renamed argument `writable` as `waiting` * hosited out creating and raising exception * turned into a `switch`
2020-04-17fileutils now depends on rbconfig.rb due to JRuby supportNobuyoshi Nakada
2020-04-17Suppress C4267 "possible loss of data" warningsNobuyoshi Nakada
Just cast down explicitly.
2020-04-17test/ruby/test_process.rb: Skip GID.from_name on AndroidYusuke Endoh
The user management on Android seems very different https://rubyci.org/logs/rubyci.s3.amazonaws.com/android28-x86_64/ruby-master/log/20200416T234122Z.fail.html.gz
2020-04-17Remove lib/rss.rbSutou Kouhei
This is a follow-up of 83240f315a10b42b53c3b62c1fbc428f97912665 .
2020-04-17Suppress C4267 "possible loss of data" warningsNobuyoshi Nakada
2020-04-17* 2020-04-17 [ci skip]git
2020-04-17core_assertions.rb: fixed fd leak at timeoutNobuyoshi Nakada
Notes: Merged: https://github.com/ruby/ruby/pull/3039
2020-04-17envutil.rb: not try to close pipes twiceNobuyoshi Nakada
Notes: Merged: https://github.com/ruby/ruby/pull/3039
2020-04-16Preserve encoding in error messages for invalid user/group nameNobuyoshi Nakada
2020-04-16Added tests for Process::UID.from_name and Process::GID.from_nameNobuyoshi Nakada
2020-04-16Preserve encoding in error message for invalid env exec optionNobuyoshi Nakada
2020-04-16Added test for invalid env exec optionNobuyoshi Nakada
2020-04-16Moved noreturn call to end of noreturn functionNobuyoshi Nakada
2020-04-16Use UNREACHABLE_RETURN for non-void functionNobuyoshi Nakada
2020-04-16fix compiler error on gcc 4.x卜部昌平
It seems gcc prior to 5 suffered from preprocessor bug. We have to provide workarounds. See https://github.com/ruby/ruby/runs/591138012 ---- Here is something interesting. According to C99, strictly speaking, the gcc behaviour was in fact legal(!) and everything else were wrong. This was not a bug of gcc, rather a bug of the ISO C Standard. This defect was reported to the committee as DR#412, and fixed accordingly. All tested compilers now conform C17's updated preprocessor description. See http://www.open-std.org/JTC1/SC22/WG14/www/docs/dr_412.htm
2020-04-16* 2020-04-16 [ci skip]git
2020-04-16Support for FreeBSD <sys/cdefs.h>卜部昌平
FreeBSD's <sys/cdefs.h> is broken. Cygwin is also affected by that. We need to avoid using them. See also: https://github.com/freebsd/freebsd/commit/d1c67819db000c02d3a9c79f3651c10aeedad1a0 https://sourceware.org/git/?p=newlib-cygwin.git;a=commit;f=newlib/libc/include/sys/cdefs.h;h=44d6d53977e6bc82c2b1e6dbe8ae7f310b260604
2020-04-15Raise EPIPE at broken pipe for the backward compatibilityNobuyoshi Nakada
Instead of SignalException for SIGPIPE, raise `Errno::EPIPE` with instance variable `signo` and re-send that signal at exit. [Feature #14413] Notes: Merged: https://github.com/ruby/ruby/pull/3035
2020-04-15Added rb_syserr_new_pathNobuyoshi Nakada
Similar to rb_syserr_fail_path, but just returns the created exception instance instead of raising it. Notes: Merged: https://github.com/ruby/ruby/pull/3035
2020-04-15Create succ_index_table as a part of `iseq_setup`Nobuyoshi Nakada
With compiling `CPDEBUG >= 2`, `rb_iseq_disasm` segfaults if this table has not been created. Also `ibf_load_iseq_each` calls `rb_iseq_insns_info_encode_positions`. Notes: Merged: https://github.com/ruby/ruby/pull/3033
2020-04-15Added test for `debug_level:` option of `RubyVM::InstructionSequence.compile`Nobuyoshi Nakada
Notes: Merged: https://github.com/ruby/ruby/pull/3033
2020-04-14This test is not testing attr_writerTakashi Kokubun
2020-04-14Invalidate fastpath when calling attr_reader by superTakashi Kokubun
The same bug as 8355a99883 existed in attr_reader too.
2020-04-14Invalidate fastpath when calling attr_writer by superTakashi Kokubun
We started to use fastpath on invokesuper when a method is not refinements since 5c27681813, but we shouldn't have used fastpath for attr_writer either. `cc->aux_.attr_index` is for an actual receiver class, while we store its superclass in `cc->klass` and therefore there's no way to properly invalidate attr_writer's inline cache when it's called by super. [Bug #16785] I suspect the same bug also exists in attr_reader. I'll address that in another commit.
2020-04-15Disassemble nop-inserted listNobuyoshi Nakada
2020-04-15Show heading for update_catch_except_flagsNobuyoshi Nakada
2020-04-15Shrink diassembled result stringNobuyoshi Nakada
2020-04-15* 2020-04-15 [ci skip]git
2020-04-15Disallow line-continuation before R-assignNobuyoshi Nakada
2020-04-14Removed duplicate value_expr checksNobuyoshi Nakada
`arg_rhs` has the same check and is always a non-void value expression.
2020-04-13Fix logic to detect vs120Takashi Kokubun
MJIT_CC seems not defined https://ci.appveyor.com/project/ruby/ruby/builds/32161572/job/u5sw8yn4in87heki
2020-04-14[ruby/date] Suppress -Wchar-subscripts warnings by Cygwin gcc 9.3.0Nobuyoshi Nakada
https://github.com/ruby/date/commit/9968eb69f0
2020-04-13Add missing call in 70b7304f03Takashi Kokubun
2020-04-13Ignore AppVeyor vs120's pdb corruptionTakashi Kokubun
We tried to fix this like https://github.com/ruby/ruby/pull/3029, but it didn't work. The failure has never been helpful for developing MJIT, and currently it's not prioritized to be fixed. Until we try to figure out the root cause on AppVeyor vs120, let's optionally disable testing when the random corruption happens.
2020-04-13Unify vm benchmark prefixes to vm_ (#3028)Takashi Kokubun
The vm1_ prefix and vm2_ had had special meaning until 820ad9cb1d72d0897b73dae282df3793814b27e8 and 12068aa4e980ab32a0438408a519030e65dabf5e. AFAIK there's no special meaning in vm3_ prefix. As they have confused people (like "In `benchmark` what is difference between `vm1_`, `vm2_` and `vm3_`"), I'd like to remove the obsoleted prefix as we obviated that two years ago. Notes: Merged-By: k0kubun <takashikkbn@gmail.com>
2020-04-14Make y.output in ripper unlocalized [ci skip]Nobuyoshi Nakada
Often it is easy to search, grep, etc from command line, for debugging purpose.