| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Rename --jit to --mjit
[Feature #18349]
* Fix a few more --jit references
* Fix MJIT Actions
* More s/jit/mjit/ and re-introduce --disable-jit
* Update NEWS.md
* Fix test_bug_reporter_add
|
|
|
|
|
| |
It results in a circular dependency when `--with-ruby-pc=ruby.pc`
is given. [ci skip]
|
|
|
|
|
|
|
|
| |
The old URL
http://mail.opensolaris.org/pipermail/dtrace-discuss/2005-August/000207.html
pointed to the official archive of dtrace-discuss mailing list
in opensolaris.org, disappeared in 2013.
The new URL points to the MARC Mailing list ARChives.
|
|
|
|
|
| |
This commit removes usages of rb_gc_force_recycle since it is a burden
to maintain and makes changes to the GC difficult.
|
|
|
|
|
| |
Now that we're using the jit function entry point, we don't need the
scraper. Thank you for your service, scraper. ❤️
|
|
|
|
| |
Just happened to run across this, so lets fix them
|
|
|
|
| |
Renaming uJIT to YJIT. AKA s/ujit/yjit/g.
|
| |
|
| |
|
| |
|
|
|
|
| |
Less macros == huge win.
|
|
|
|
|
| |
Extension gems will be installed by the installed standard
libraries.
|
|
|
|
|
| |
* Get rid of command substitution for cmd.exe.
* Separate RM1 command to remove single file sans directory.
|
|
|
|
| |
applied doxygen -g for Doxygen 1.9.3.
|
|
|
|
|
|
| |
This prevents file-static functions/variables be listed in the CAPI
documents. An entity shall be placed inside of a file that contains
`@file` doxygen comment, in order for it to be documented. [ci skip]
|
|
|
|
|
|
|
|
|
| |
I often feel that C API documents are lacked in C source codes,
especially for static functions. I propose to turn EXTRACT_STATIC = YES
flag of Doxygen to YES, and write document comments for static functions
as much as possible.
* template/Doxyfile.tmpl: EXTRACT_STATIC: YES [Bugs #14037]
|
|
|
|
|
|
|
| |
I guess we don't want documents for C API of extension libraries? They
are never intended to provide C APIs anyways.
We could revisit this decision later. [ci skip]
|
|
|
|
| |
Must not be a bad idea to improve documents. [ci skip]
|
|
|
|
| |
Asked ko1 about the design. [ci skip]
|
|
|
|
| |
Must not be a bad idea to improve documents. [ci skip]
|
|
|
|
| |
Must not be a bad idea to improve documents. [ci skip]
|
|
|
|
| |
Must not be a bad idea to improve documents. [ci skip]
|
|
|
|
| |
Must not be a bad idea to improve documents. [ci skip]
|
|
|
|
|
| |
This enables me to write `@shyouhei` in C comments without complained by
doxygen that @shyouhei is an unknown special command. [ci skip]
|
|
|
|
| |
It is easier to maintain (e.g. sort them). [ci skip]
|
|
|
|
|
|
|
|
| |
The new Doxyfile.tmpl says:
> # Values that contain spaces should be placed between quotes (\" \").
[ci skip]
|
|
|
|
|
|
|
|
| |
`make capi` warned:
> warning: Included by graph for 'dllexport.h' not generated, too many nodes (85)
[ci skip]
|
|
|
|
| |
Let our VCS manage old contents. [ci skip]
|
|
|
|
|
|
|
|
|
| |
Didn't question the current settings. This changeset just re-applied
`doxygen -g` against:
doxygen 1.9.0 (1e72202d8fa0e9d2b3f2a29c88ec4f5790a0a4e2)
[ci skip]
|
|
|
|
|
| |
Expand variables undefined in configure.ac, RUBY_RELEASE_DATE and
so on.
|
|
|
|
| |
So that it is no longer needed in ruby.pc.in.
|
|
|
|
| |
Moved variables obviously independent from others first.
|
|
|
|
|
| |
Get rid of tons of linker warnings that it could not find object
file symbol for every symbols, when targeting darwin.
|
| |
|
|
|
|
|
|
| |
This reverts commit ac86fcbfd0bab8667d277aa575bc5b81e5135d3c.
This change broke "--disable-shared --with-static-linked-ext".
|
|
|
|
| |
It is included in libruby, which is linked into the main programs.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
* See [Feature #17752]
Co-authored-by: xtkoba (Tee KOBAYASHI) <xtkoba+ruby@gmail.com>
|
|
|
|
| |
Not all preprocessors work with output option.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This reverts commit 331f0bc1cb7965bec9aed5d7278360c2e9fc8946.
It seems a mistake.
|
| |
|
|
|
|
|
|
|
|
| |
because the name "MJIT" is an internal code name, it's inconsistent with
--jit while they are related to each other, and I want to discourage future
JIT implementation-specific (e.g. MJIT-specific) APIs by this rename.
[Feature #17490]
|
| |
|