- 11 5月, 2020 12 次提交
-
-
由 卜部昌平 提交于
SunPro's #pragma does_not_return(...) needs an argument. That does not fit the attribute syntax we employ.
-
由 卜部昌平 提交于
This header file is simply out of date (for decades since at least 1989). It's the 21st century. Just stop using it.
-
由 卜部昌平 提交于
https://gcc.gnu.org/onlinedocs/gcc/Other-Builtins.html says: > GCC never returns 1 when you call the inline function with a string > constant or ... Because rb_str_new and familiy take string constants, it was a bad idea for them to contain RB_CONSTANT_P. We should instead do so in corresponding macros. [ruby-core:98212]
-
由 卜部昌平 提交于
To fix build failures.
-
由 卜部昌平 提交于
Devs do not love "impl".
-
由 卜部昌平 提交于
-
由 卜部昌平 提交于
-
由 卜部昌平 提交于
Devs do not love "3". The only exception is RUBY3_KEYWORDS in parse.y, which seems unrelated to our interests.
-
由 卜部昌平 提交于
This shall fix compile errors.
-
由 卜部昌平 提交于
Devs do not love "3".
-
由 Nobuyoshi Nakada 提交于
Many tools under tool directory haven't worked with ruby 1.8.
-
由 Nobuyoshi Nakada 提交于
-
- 10 5月, 2020 14 次提交
-
-
由 Nobuyoshi Nakada 提交于
-
由 Nobuyoshi Nakada 提交于
-
由 git 提交于
-
由 Nobuyoshi Nakada 提交于
GNU make does not export it by default.
-
由 Nobuyoshi Nakada 提交于
https://gcc.gnu.org/gcc-10/changes.html#c > * GCC now defaults to `-fno-common`. As a result, global > variable accesses are more efficient on various targets. In > C, global variables with multiple tentative definitions now > result in linker errors. With `-fcommon` such definitions are > silently merged during linking.
-
由 Nobuyoshi Nakada 提交于
-
由 Nobuyoshi Nakada 提交于
`RubyVM.each_builtin` is not defined when cross compiling.
-
由 Takashi Kokubun 提交于
not only when !w but also when w == WAITPID_LOCK_ONLY. See also: f7c0cc36 and a2264342. We thought this change was an oversight in the latter commit. Without this change, the test fails like: $ make test-all TESTS="../test/ruby/test_process.rb -n test_exec_failure_leaves_no_child" RUN_OPTS="--jit" ... 1) Failure: TestProcess#test_exec_failure_leaves_no_child [/home/k0kubun/src/github.com/ruby/ruby/test/ruby/test_process.rb:2493]: Expected [[26799, #<Process::Status: pid 26799 exit 127>]] to be empty. Co-Authored-By: NYusuke Endoh <mame@ruby-lang.org>
-
由 卜部昌平 提交于
Fix MSVC build error.
-
由 卜部昌平 提交于
To generate what is necessary via generic_erb.rb instead.
-
由 卜部昌平 提交于
To generate what is necessary via generic_erb.rb instead.
-
由 Takashi Kokubun 提交于
with MJIT worker enabled The problem: ``` $ ruby -ropen3 --jit -e 'Open3.capture2e("cmake") rescue nil;binding.irb' irb(main)[01:0]> Process.waitall => [[10656, #<Process::Status: pid 10656 exit 127>]] $ ruby -ropen3 -e 'Open3.capture2e("cmake") rescue nil;binding.irb' irb(main)[01:0]> Process.waitall => [] ``` Not sure why it's happening yet, but first I'd like to prevent trunk-mjit-wait from failing like http://ci.rvm.jp/results/trunk-mjit-wait@silicon-docker/2929075.
-
由 git 提交于
-
由 Yusuke Endoh 提交于
just for a case. In addition, this change suppresses unused variable warning.
-
- 09 5月, 2020 14 次提交
-
-
由 卜部昌平 提交于
-
由 Nobuyoshi Nakada 提交于
-
由 Yusuke Endoh 提交于
https://rubyci.org/logs/rubyci.s3.amazonaws.com/solaris10-gcc/ruby-master/log/20200509T100003Z.fail.html.gz ``` 1) Failure: TestIO_Console#test_failed_path [/export/home/users/chkbuild/cb-gcc/tmp/build/20200509T100003Z/ruby/test/io/console/test_io_console.rb:40]: [Errno::ENODEV, Errno::ENOTTY, Errno::EBADF] exception expected, not #<Errno::ENXIO: No such device or address - /dev/null>. ```
-
由 Hiroshi SHIBATA 提交于
-
由 Nobuyoshi Nakada 提交于
May fail with ENOTTY instead of ENODEV. https://github.com/ruby/io-console/commit/fe117b89e0
-
由 Kazuhiro NISHIYAMA 提交于
-
由 Kazuhiro NISHIYAMA 提交于
-
由 Nobuyoshi Nakada 提交于
-
由 Nobuyoshi Nakada 提交于
-
由 Nobuyoshi Nakada 提交于
-