aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Directly mark compile options from the AST objectAaron Patterson2019-08-272-2/+2
| | | | | | | `rb_ast_t` holds a reference to this object, so it should mark the object. Currently it is relying on the `mark_ary` on `node_buffer` to ensure that the object stays alive. But since the array internals can move, this could cause a segv if compaction impacts the array.
* Fix doxygen actionKazuhiro NISHIYAMA2019-08-281-26/+10
| | | | | | | - Fix checkout error: `fatal: destination path '.' already exists and is not an empty directory.` - Remove `GITHUB_SHA` in env, because set automatically https://help.github.com/en/articles/virtual-environments-for-github-actions#environment-variables - Change minute from 0 to 20 for test soon
* Run on schedule only and skip if not modifiedKazuhiro NISHIYAMA2019-08-281-17/+35
|
* Remove jquery.jsaycabta2019-08-281-2/+0
|
* Stop passing CC_LIBS in compile_c_to_oTakashi Kokubun2019-08-281-1/+1
| | | | | | | | | | | | | | To fix "gcc: -lgcc: linker input file unused because linking not done" in https://rubyci.org/logs/rubyci.s3.amazonaws.com/openbsd65/ruby-master/log/20190826T200009Z.log.html.gz Still I'm intentionally leaving CC_DLDFLAGS_ARGS because making compiler options different might result in compile/link failure. (Of course CC_DLDFLAGS_ARGS usually should not have compiler options, but it might include by bad configure setup) The same problem may exist in MJIT_LIBS used inside CC_LIBS as well, but I just ignored that case because it impacts only MinGW / cygwin, hoping that their users do not perform a wrong configure.
* Version 6.2.0aycabta2019-08-281-1/+1
|
* Good bye jQueryaycabta2019-08-286-179/+92
|
* Treat RUBY_REVISION as an integer on old rubiesNAKAMURA Usaku2019-08-281-4/+8
|
* Make doxygen / coverage torelant to clone raceTakashi Kokubun2019-08-282-4/+4
| | | | | | | | | | | a little. Doing both `git clone --depth=1` and `git reset --hard ${sha}` does not make sense (the latter command either does nothing or just fails), so I added non-1 value as a depth. Maybe we don't need depth=50 for pull_request and schedule, so it's 10 for now.
* * 2019-08-28 [ci skip]git2019-08-281-1/+1
|
* Follows callback declaration updatesNobuyoshi Nakada2019-08-284-11/+16
|
* Drop more unused configs from doxygen and coverageTakashi Kokubun2019-08-272-16/+0
| | | | workflows, because mame said he has never seen it.
* Omit unused matrix strategy from doxygen workflowTakashi Kokubun2019-08-271-4/+0
|
* Short revision of SVN should be an IntegerNobuyoshi Nakada2019-08-271-1/+1
|
* Fix rb_thread_create argument typeTakashi Kokubun2019-08-271-1/+1
| | | | | | | | | | in response to the declaration change in e3fc30564e9466d6926f9d25a090dcf787bd5c33. Fixing the AppVeyor mswin CI failure: https://ci.appveyor.com/project/ruby/ruby/builds/26980881/job/2j6h1qwjnbc8cpop ref: https://github.com/ruby/ruby/pull/2404
* Add graphviz for dot commandKazuhiro NISHIYAMA2019-08-271-1/+1
|
* Doxygen in GitHub Actions (#2406)Yusuke Endoh2019-08-271-0/+62
| | | * .github/workflows/doxygen.yml: add a workflow for doxygen in Actions
* delete `$` sign from C identifiers卜部昌平2019-08-274-12/+12
| | | | | They lack portability. See also https://travis-ci.org/shyouhei/ruby/jobs/577164015
* rb_uninterruptible now free from ANYARGS卜部昌平2019-08-272-2/+2
| | | | | | After 5e86b005c0f2ef30df2f9906c7e2f3abefe286a2, I now think ANYARGS is dangerous and should be extinct. This function has only one call site so adding appropriate prototype is trivial.
* struct MEMO now free from ANYARGS卜部昌平2019-08-272-2/+2
| | | | | | | After 5e86b005c0f2ef30df2f9906c7e2f3abefe286a2, I now think ANYARGS is dangerous and should be extinct. There is only one usage of MEMO::u3::func in load.c (where void Init_Foobar(vodi) is registered) so why not just be explicit.
* rb_ivar_foreach now free from ANYARGS卜部昌平2019-08-272-6/+8
| | | | | | | After 5e86b005c0f2ef30df2f9906c7e2f3abefe286a2, I now think ANYARGS is dangerous and should be extinct. This commit adds a function prototype for rb_ivar_foreach. Luckily this change revealed no problematic usage of the function.
* rb_hash_foreach now free from ANYARGS卜部昌平2019-08-275-20/+34
| | | | | | | After 5e86b005c0f2ef30df2f9906c7e2f3abefe286a2, I now think ANYARGS is dangerous and should be extinct. This commit adds function prototypes for rb_hash_foreach / st_foreach_safe. Also fixes some prototype mismatches.
* rb_define_hooked_variable now free from ANYARGS卜部昌平2019-08-2710-60/+94
| | | | | | | | | After 5e86b005c0f2ef30df2f9906c7e2f3abefe286a2, I now think ANYARGS is dangerous and should be extinct. This commit uses rb_gvar_getter_t / rb_gvar_setter_t for rb_define_hooked_variable / rb_define_virtual_variable which revealed lots of function prototype inconsistencies. Some of them were literally decades old, going back to dda5dc00cff334cac373096d444a0fd59e716124.
* struct st_hash_type now free from ANYARGS卜部昌平2019-08-272-5/+22
| | | | | | | After 5e86b005c0f2ef30df2f9906c7e2f3abefe286a2, I now think ANYARGS is dangerous and should be extinct. This commit adds function prototypes for struct st_hash_type. Honestly I don't understand why they were commented out at the first place.
* st_foreach now free from ANYARGS卜部昌平2019-08-278-19/+33
| | | | | | | | After 5e86b005c0f2ef30df2f9906c7e2f3abefe286a2, I now think ANYARGS is dangerous and should be extinct. This commit deletes ANYARGS from st_foreach. I strongly believe that this commit should have had come with b0af0592fdd9e9d4e4b863fde006d67ccefeac21, which added extra parameter to st_foreach callbacks.
* rb_thread_create now free from ANYARGS卜部昌平2019-08-274-5/+5
| | | | | | After 5e86b005c0f2ef30df2f9906c7e2f3abefe286a2, I now think ANYARGS is dangerous and should be extinct. This commit deletes ANYARGS from rb_thread_create, which seems very safe to do.
* rb_proc_new / rb_fiber_new now free from ANYARGS卜部昌平2019-08-275-13/+13
| | | | | | | After 5e86b005c0f2ef30df2f9906c7e2f3abefe286a2, I now think ANYARGS is dangerous and should be extinct. This commit deletes ANYARGS from rb_proc_new / rb_fiber_new, and applies RB_BLOCK_CALL_FUNC_ARGLIST wherever necessary.
* rb_catch now free from ANYARGS卜部昌平2019-08-273-7/+7
| | | | | | After 5e86b005c0f2ef30df2f9906c7e2f3abefe286a2, I now think ANYARGS is dangerous and should be extinct. This commit deletes ANYARGS from rb_catch, and fixes some bugs revealed by that.
* rb_ensure now free from ANYARGS卜部昌平2019-08-2717-37/+62
| | | | | | After 5e86b005c0f2ef30df2f9906c7e2f3abefe286a2, I now think ANYARGS is dangerous and should be extinct. This commit deletes ANYARGS from rb_ensure, which also revealed many arity / type mismatches.
* rb_rescue / rb_rescue2 now free from ANYARGS卜部昌平2019-08-278-18/+20
| | | | | | After 5e86b005c0f2ef30df2f9906c7e2f3abefe286a2, I now think ANYARGS is dangerous and should be extinct. This commit deletes ANYARGS from rb_rescue / rb_rescue2, which revealed many arity / type mismatches.
* rb_iterate now takes rb_block_call_func_t卜部昌平2019-08-273-3/+3
| | | | | | After 5e86b005c0f2ef30df2f9906c7e2f3abefe286a2, I now think ANYARGS is dangerous and should be extinct. This commit makes rb_iterate free from ANYARGS.
* decouple compile.c usage of imemo_ifunc卜部昌平2019-08-277-36/+56
| | | | | | | After 5e86b005c0f2ef30df2f9906c7e2f3abefe286a2, I now think ANYARGS is dangerous and should be extinct. This commit deletes ANYARGS from struct vm_ifunc, but in doing so we also have to decouple the usage of this struct in compile.c, which (I think) is an abuse of ANYARGS.
* #define RB_BLOCK_CALL_FUNC_STRICT 1卜部昌平2019-08-273-10/+6
| | | | | | After 5e86b005c0f2ef30df2f9906c7e2f3abefe286a2, I now think ANYARGS is dangerous and should be extinct. Let's start from making rb_block_call_func_t strict, and apply RB_BLOCK_CALL_FUNC_ARGLIST liberally.
* fix function prototype mismatch of rb_block_call卜部昌平2019-08-271-2/+2
| | | | Nobu missed it in f0e73fc9862c8d2c57a89349fb79012b826b8245.
* delete rb_method_defined_by declaration.卜部昌平2019-08-271-1/+0
| | | | Ko1 missed this in d5893b91faa7dc77ca6c9728d1054dabd757aead.
* Revert "Explain which test task"Nobuyoshi Nakada2019-08-272-4/+4
| | | | | | This reverts commit 9bc1667a188392b94971b9b96507af76cbd5f413. `name` lines are not expanded.
* .github/workflows/coverage.yml: add a cron job for coverage in ActionsYusuke Endoh2019-08-271-0/+68
|
* Explain which test taskNobuyoshi Nakada2019-08-272-4/+4
|
* Use array indexing with considering clang's feelingNobuyoshi Nakada2019-08-271-1/+1
| | | | | | | | | | | | | | | | | ``` In file included from sprintf.c:1256: ./vsnprintf.c:833:8: warning: adding 'int' to a string does not append to the string [-Wstring-plus-int] IS_PRI_EXTRA_MARK(fmt)) { ^~~~~~~~~~~~~~~~~~~~~~ ./vsnprintf.c:826:34: note: expanded from macro 'IS_PRI_EXTRA_MARK' strncmp((s)+1, PRI_EXTRA_MARK+1, \ ~~~~~~~~~~~~~~^~ ./vsnprintf.c:833:8: note: use array indexing to silence this warning ./vsnprintf.c:826:34: note: expanded from macro 'IS_PRI_EXTRA_MARK' strncmp((s)+1, PRI_EXTRA_MARK+1, \ ^ 1 warning generated. ```
* compile.c: remove const from the first argument of dladdrYusuke Endoh2019-08-271-1/+1
| | | | Unfortunately, dladdr accepts void*, not const void*, in Solaris.
* signal.c: Don't mark ruby_abort as NORETURN on SolarisYusuke Endoh2019-08-271-0/+2
| | | | | | | | | | | to suppress a warning. ``` signal.c: In function 'ruby_abort': signal.c:987:1: warning: 'noreturn' function does return } ^ ```
* Fix the appropriate C++ compiler in OS X selectionKazuhiro NISHIYAMA2019-08-271-5/+5
| | | | | Merge space and slash to character class and add missing `CXX=` before `=g++-4.2` at 5e10cb04e88c8a95ee44f6cad2bdf264e0dff92a
* Added license comment [Bug #12230] [ci skip]Nobuyoshi Nakada2019-08-271-0/+1
|
* Remove duplicated delegationaycabta2019-08-271-1/+0
|
* Delegete an instance method to a class method correctlyaycabta2019-08-271-1/+1
|
* this iv table should also use the new update functionAaron Patterson2019-08-261-1/+1
|
* Save value to @ambiguous_width because of a accessoraycabta2019-08-271-3/+3
|
* Pick lib/readline.rb from ruby/relineaycabta2019-08-271-1/+2
|
* The "private" doesn't make sence for class methods and a constantaycabta2019-08-271-2/+0
|
* Use preposing "private" to define methodsaycabta2019-08-271-6/+4
|
generated by cgit v1.2.3 (git 2.39.1) at 2024-09-30 12:20:47 +0000