| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
|
|
| |
https://rubyci.s3.amazonaws.com/solaris10-sunc/ruby-master/log/20220428T000004Z.fail.html.gz
```
linking static-library libruby-static.a
/bin/sh: syntax error at line 8: `(' unexpected
gmake: *** [Makefile:318: libruby-static.a] Error 2
exit 2
failed(make)
```
|
|
|
|
|
|
|
|
| |
The shell in Solaris 10 has trouble understanding the syntax I used in
YJIT's library merging script.
This commit reduces the code the shell needs to parse before exiting on
non-YJIT builds to hopefully fix the error on Solaris.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In December 2021, we opened an [issue] to solicit feedback regarding the
porting of the YJIT codebase from C99 to Rust. There were some
reservations, but this project was given the go ahead by Ruby core
developers and Matz. Since then, we have successfully completed the port
of YJIT to Rust.
The new Rust version of YJIT has reached parity with the C version, in
that it passes all the CRuby tests, is able to run all of the YJIT
benchmarks, and performs similarly to the C version (because it works
the same way and largely generates the same machine code). We've even
incorporated some design improvements, such as a more fine-grained
constant invalidation mechanism which we expect will make a big
difference in Ruby on Rails applications.
Because we want to be careful, YJIT is guarded behind a configure
option:
```shell
./configure --enable-yjit # Build YJIT in release mode
./configure --enable-yjit=dev # Build YJIT in dev/debug mode
```
By default, YJIT does not get compiled and cargo/rustc is not required.
If YJIT is built in dev mode, then `cargo` is used to fetch development
dependencies, but when building in release, `cargo` is not required,
only `rustc`. At the moment YJIT requires Rust 1.60.0 or newer.
The YJIT command-line options remain mostly unchanged, and more details
about the build process are documented in `doc/yjit/yjit.md`.
The CI tests have been updated and do not take any more resources than
before.
The development history of the Rust port is available at the following
commit for interested parties:
https://github.com/Shopify/ruby/commit/1fd9573d8b4b65219f1c2407f30a0a60e537f8be
Our hope is that Rust YJIT will be compiled and included as a part of
system packages and compiled binaries of the Ruby 3.2 release. We do not
anticipate any major problems as Rust is well supported on every
platform which YJIT supports, but to make sure that this process works
smoothly, we would like to reach out to those who take care of building
systems packages before the 3.2 release is shipped and resolve any
issues that may come up.
[issue]: https://bugs.ruby-lang.org/issues/18481
Co-authored-by: Maxime Chevalier-Boisvert <maximechevalierb@gmail.com>
Co-authored-by: Noah Gibbs <the.codefolio.guy@gmail.com>
Co-authored-by: Kevin Newton <kddnewton@gmail.com>
|
|
|
|
|
|
|
|
|
| |
Previously, `make test-spec` was not printing the description with +YJIT
even when YJIT was indeed enabled. It was confusing on CI. `fake.rb` was
changing the `RUBY_DESCRIPTION` constant incorrectly.
I suppose `make test-spec` mostly needs the `mkmf` faking and not the
faking of `RUBY_.*` constants, so maybe there is an opportunity to simplify
in the future.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
So that `mkmf` checks work from `make run`, and also remove
duplicate `$(MINIRUBYOPT)` which is used in `$(MINIRUBY)`.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This is another attempt to fix out-of-src build with
--with-static-linked-ext. The first attempt was
4f1888bda70981d9f5b1bf55ab692e0ce18e79f4 but reverted because it broke
out-of-src build from pre-generated sources via `make dist`.
This patch fixes the second trans C source gen, mentioned in the
previous commit message, by passing MINIRUBY as well as when invoking
from common.mk
|
|
|
|
|
| |
IA64 support was dropped in ticket #15894, so we can drop support for
HP-UX.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* 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.
|
| |
|