aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* [ruby/prime] Improve docs for Prime.include? (#7)Marcus Stollsteimer2020-03-061-1/+2
| | | | https://github.com/ruby/prime/commit/230a5af325
* [ruby/prime] Fix Prime.include?Jeremy Evans2020-03-062-0/+20
| | | | | | | | | | | | | | | Previously, it would be an infinite loop if passed a non-prime integer. Also, Prime.include? should also provide similar results to Module#include? if passed a Module, so handle that. For consistency with Enumerable#include?, return false if passed other object types. Fixes Ruby Bug 10167. https://github.com/ruby/prime/commit/55dda6aa7f
* * 2020-03-06 [ci skip]git2020-03-061-1/+1
|
* Mask RubyVM-specific testCharles Oliver Nutter2020-03-051-6/+8
|
* spec/ruby/core/process/exec_spec.rb: remove a guard for openbsdYusuke Endoh2020-03-051-10/+2
| | | | | | openbsd current seems to behave the same as other OSs. https://rubyci.org/logs/rubyci.s3.amazonaws.com/openbsd-current/ruby-master/log/20200305T063005Z.fail.html.gz
* Renamed `lex_flags` as `lex_context`Nobuyoshi Nakada2020-03-051-49/+49
|
* Fixed a typoNobuyoshi Nakada2020-03-051-1/+1
|
* [win32] get rid of redefinition of reserved macroNobuyoshi Nakada2020-03-051-0/+2
| | | | | | ``` warning C4117: macro name '_INTEGRAL_MAX_BITS' is reserved, '#define' ignored ```
* * 2020-03-05 [ci skip]git2020-03-051-1/+1
|
* [ruby/fiddle] always use ffi_closure_alloc on WindowsNobuyoshi Nakada2020-03-051-1/+6
|
* Fixed FD leakNobuyoshi Nakada2020-03-041-0/+2
|
* [ruby/fiddle] use ffi_closure_alloc only with 3.2 or laterNobuyoshi Nakada2020-03-041-4/+2
|
* [win32] suppress false warning by mingw gccNobuyoshi Nakada2020-03-042-2/+2
|
* [win32] suppress false warning by MSVCNobuyoshi Nakada2020-03-041-1/+2
|
* Fixed never-defined symbol nameNobuyoshi Nakada2020-03-041-1/+1
|
* [ruby/fiddle] ffi_closure_free is available in the bundled libffiNobuyoshi Nakada2020-03-041-1/+3
|
* [ruby/fiddle] Use ffi_closure_free if availableNobuyoshi Nakada2020-03-042-6/+4
|
* Revert "Revert "Revert "[ruby/fiddle] Use ffi_closure_free by default. (#20)"""Yusuke Endoh2020-03-042-6/+42
| | | | | | | | | | | | | | | | | | | | This reverts commit 87f6154bb4c67ca77ee353bb1fe25a922036c0e5. It turned out that the change fails to build on macOS https://rubyci.org/logs/rubyci.s3.amazonaws.com/osx1014/ruby-master/log/20200304T074503Z.fail.html.gz ``` + make 'TESTS=--hide-skip -v fiddle' RUBYOPT=-w test-all dyld: lazy symbol binding failed: Symbol not found: _ffi_closure_alloc Referenced from: /Users/hsbt/Documents/cb/tmp/build/20200304T074503Z/ruby/.ext/x86_64-darwin18/fiddle.bundle Expected in: flat namespace dyld: Symbol not found: _ffi_closure_alloc Referenced from: /Users/hsbt/Documents/cb/tmp/build/20200304T074503Z/ruby/.ext/x86_64-darwin18/fiddle.bundle Expected in: flat namespace make: *** [yes-test-all] Abort trap: 6 ```
* Revert "Revert "[ruby/fiddle] Use ffi_closure_free by default. (#20)""Yusuke Endoh2020-03-042-42/+6
| | | | | | | | | | | | | | | This reverts commit efd641ffab34e433a8d8a7d78914576f2425aa90. This changeset seems to be needed to suppress a warning on Ubuntu 20.04 https://rubyci.org/logs/rubyci.s3.amazonaws.com/ubuntu/ruby-master/log/20200304T033004Z.log.html.gz ``` closure.c:264:5: warning: 'ffi_prep_closure' is deprecated: use ffi_prep_closure_loc instead [-Wdeprecated-declarations] 264 | result = ffi_prep_closure(pcl, cif, callback, (void *)self); | ^~~~~~ ``` I guess there was a reason why the commit was reverted (maybe some CIs failed?), so try it again.
* test/lib/jit_support.rb: The path to icc was changedYusuke Endoh2020-03-041-1/+1
|
* suppress uninitialized variable warnings卜部昌平2020-03-042-2/+2
| | | | | | Starting GCC 7, warnings about uninitialized variables are issued around them. Such warnings could be false positives (all versions of clang do not warn), but adding initializers there could never be bad things.
* tool/lib/test/unit: support TESTS='-- -ext-' again卜部昌平2020-03-041-1/+1
| | | | | | | There is a test directory named test/-ext-. Because this directry starts with a hyphen, we have to cheat test/unit in order for it to run the tests underneath. TESTS='-- -ext' worked for a long time. Let's not break that maneuver.
* %p is for void *卜部昌平2020-03-042-4/+4
| | | | | | | | See also 35eb12c06397e770392a41343cbffc4b204e15c9 6f5eb285077d9abf8f97056531996c58674b570c 687308cf0dab0af675e40da2b6ab8ccd5f77c072 b6a2d63eb3dbc31e110e8cb95e054dd71d49a611
* fix compile error w/ -DUSE_TRANSIENT_HEAP=0卜部昌平2020-03-042-0/+4
| | | | | rb_transient_heap_managed_ptr_p is available only when USE_TRANSIENT_HEAP. Need #if guards.
* fix compile error w/ -DCALC_EXACT_MALLOC_SIZE卜部昌平2020-03-041-4/+0
|
* fix 6e271e4cbbe6a8bc4d4f75dc553ce054eae7af00Koichi Sasada2020-03-041-1/+1
|
* Run major GC to make sure the minor GC reasonKoichi Sasada2020-03-041-0/+1
| | | | | GC.latest_gc_info[:major_by] can return `oldmalloc` because of last GC status.
* Run major GC to make sure the minor GC next time.Koichi Sasada2020-03-041-1/+2
| | | | | | `GC.start(full_mark: false)` can run full GC because of last GC status. Just after major GC, the possibility to run major GC next time is too small (not a zero, but too small possibility).
* Narrow the check target.Koichi Sasada2020-03-041-1/+4
| | | | | Call GC.verify_internal_consistency only for Gem related test on i386-solaris.
* * 2020-03-04 [ci skip]git2020-03-041-1/+1
|
* Don't tweak RubyVM compile options if it's not definedCharles Oliver Nutter2020-03-031-6/+10
|
* Limit the debug code conditon so that it runs only under i386-solarisYusuke Endoh2020-03-031-1/+1
|
* Suppress an "assigned but unused variable" warningYusuke Endoh2020-03-031-0/+1
|
* [DOC] Separated parenthesized notes from subsection headingsNobuyoshi Nakada2020-03-031-4/+12
| | | | | As the headings become link anchors, remove less useful notes. [ci skip]
* Preserve `kwarg` flag and fix up f5c904c2a9Nobuyoshi Nakada2020-03-032-0/+4
|
* add debug code for SolarisKoichi Sasada2020-03-031-0/+1
| | | | | Check heap consistency after each test to debug. https://rubyci.org/logs/rubyci.s3.amazonaws.com/unstable11x/ruby-master/log/20200303T012406Z.fail.html.gz
* Ignore incompatible convert of symbolsKoichi Sasada2020-03-031-0/+2
|
* Convert incompatible encoding symbol namesaycabta2020-03-031-1/+3
|
* * 2020-03-03 [ci skip]git2020-03-031-1/+1
|
* method_missing_reason should be set.Koichi Sasada2020-03-031-0/+1
| | | | | | | | | | | send() has special method launcher in VM and it has special method_missing caller. This path doesn't set ec->method_missing_reason which is used at exception creation, so setup this information. Without this setting, NoMethodError exception becomes NameError. This patch will fix: http://ci.rvm.jp/results/trunk-random1@phosphorus-docker/2761643
* Suppress "assigned but unused variable" warningsYusuke Endoh2020-03-021-0/+2
|
* Reduced parser stack usage by merging non-result actionsNobuyoshi Nakada2020-03-021-14/+14
|
* Packed stacked bit flags into one structNobuyoshi Nakada2020-03-021-45/+51
|
* Add `#write` and `#binwrite` to IO section [ci skip]Kazuhiro NISHIYAMA2020-03-021-0/+2
|
* Allow newlines inside braced patternNobuyoshi Nakada2020-03-022-2/+24
|
* .github/workflows: name the configure runs卜部昌平2020-03-023-3/+5
| | | | Explicit `name:` entry was requested by @nobu.
* .github: let "make leaked-globals" run in parallel卜部昌平2020-03-023-8/+4
| | | | | This target can be a build matrix. Also it does not make sense to test it on mjit.
* .github: make use of working-directory卜部昌平2020-03-025-67/+68
| | | | | | One can specify working directory of a step, no by `cd foo` inside of the run. See also https://help.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun
* .github: less verbose on: specifier卜部昌平2020-03-025-35/+5
| | | | | | | | The `branch:` specifier was necessary before, to prevent double-testing master and trunk. Now that we no longer have trunk, we can slim the expressions. See also: https://help.github.com/en/actions/reference/workflow-syntax-for-github-actions#on
* .travis.yml, .github: delete environmental dumps卜部昌平2020-03-022-37/+0
| | | | They were necessary when developing YAMLs, but not useful any longer.