aboutsummaryrefslogtreecommitdiffstats
path: root/template
Commit message (Collapse)AuthorAgeFilesLines
* Follow up "Rework `first_lineno` to be `int`."Nobuyoshi Nakada2022-10-281-1/+1
|
* Suppress warning for fgrepHiroshi SHIBATA2022-10-191-1/+1
| | | | >fgrep: warning: fgrep is obsolescent; using ggrep -F
* Extract `RUBY_RELEASE_DATE` from also revision.hNobuyoshi Nakada2022-09-251-1/+1
| | | This make variable is very useful for daily build.
* Move mjit/instruction.rb rule to common.mkTakashi Kokubun2022-09-181-5/+0
| | | | | | as suggested by nobu. We don't really need to generate this for Windows, but using common.mk whenever possible would probably make maintenance easier.
* Introduce --basedir to insns2vm.rbTakashi Kokubun2022-09-181-2/+2
| | | | and leverage that to preserve the directory structure under tool/ruby_vm/views
* Revert "Preserve the directory structure under tool/ruby_vm/views"Takashi Kokubun2022-09-181-1/+1
| | | | | | This reverts commit 62ec621f8c7457374d1f08aec97138ac1b7bdf2a. will revisit this once fixing non-MJIT targets
* Preserve the directory structure under tool/ruby_vm/viewsTakashi Kokubun2022-09-181-1/+1
| | | | for nested target directories
* Demote mjit_instruction.rb from builtin to stdlibTakashi Kokubun2022-09-181-4/+5
|
* Fix parallel build on MINGWLars Kanis2022-09-101-0/+1
| | | | | | | | | | | | | | | | | When the build is running with a base ruby then generating `x64-ucrt-ruby320.rc` could fail due to a missing dependency to `x64-mingw-ucrt-fake.rb`. This commit adds this dependency. A failing build looks like so: ``` generating x64-mingw-ucrt-fake.rb generating x64-ucrt-ruby320.rc ../snapshot-master/win32/resource.rb:in `require': cannot load such file -- ./x64-mingw-ucrt-fake (LoadError) make: *** [GNUmakefile:57: x64-ucrt-ruby320.rc] Error 1 make: *** Waiting for unfinished jobs.... linking miniruby.exe x64-mingw-ucrt-fake.rb updated ```
* Support sub-library in builtin-loaderNobuyoshi Nakada2022-09-091-65/+5
| | | | | Previously, it was supported in prelude.c, but has not followed up the builtin-loader system.
* Move RDoc `--`/`++` directives to commentsNobuyoshi Nakada2022-09-091-1/+1
|
* Generate token ID indexes in id.defNobuyoshi Nakada2022-09-082-8/+4
| | | | | Separate the logic accross the tables from the template view for id.h.
* Fix missing replacement in 1f91dcdab3bNobuyoshi Nakada2022-09-071-1/+1
|
* Define BOOTSTRAPRUBY from HAVE_BASERUBYNobuyoshi Nakada2022-09-071-2/+5
|
* Ruby MJIT (#6028)Takashi Kokubun2022-09-041-7/+6
|
* Debugging snapshot [ci skip]Nobuyoshi Nakada2022-09-051-3/+3
|
* Fix fake.rb expansion from preprocessed version.hNobuyoshi Nakada2022-09-051-5/+4
|
* Set fake.rb variables by command line argumentsNobuyoshi Nakada2022-09-051-11/+15
| | | | Then fallbacks to preprocessed version.h.
* Make sources by BASERUBY if available instead of minirubyNobuyoshi Nakada2022-09-031-1/+1
|
* Exclude LIBPATHENV wrapper from PREPNobuyoshi Nakada2022-09-031-0/+2
|
* Move duplicate dependenciesNobuyoshi Nakada2022-09-031-5/+0
|
* Let fake.rb allow newlines in expanded stringsNobuyoshi Nakada2022-08-311-1/+3
|
* Silent configure does not output cached configurationsNobuyoshi Nakada2022-08-141-2/+3
|
* Fix race conditions when cleaning extensionsNobuyoshi Nakada2022-08-111-0/+4
| | | | | Clean built directories by `make distclean`, and then clean leftover makefiles for skipped extensions.
* The "gems" build directory was rename as ".bundle"Nobuyoshi Nakada2022-08-111-5/+5
|
* Fix paths of exts.mk to cleanNobuyoshi Nakada2022-08-111-1/+1
| | | | exts.mk files are one level under the top of extension directories.
* Add `--enable-devel` configure optionNobuyoshi Nakada2022-08-111-1/+3
| | | | | Since `RUBY_DEVEL` in cppflags has no effect in the configure script and makefiles.
* Expand tabs [ci skip]Takashi Kokubun2022-07-211-19/+19
| | | | [Misc #18891]
* Add yjit.o to DTRACE_DEPENDENT_OBJSJakub Kulík2022-05-301-1/+2
| | | | | | | | | | | | | | | | | | In principle, we have a DTrace probe in yjit.c, so yjit.o should be in DTRACE_DEPENDENT_OBJS for DTRACE_REBUILD=yes builds. This commit adds to the list. In practice DTRACE_REBUILD=yes implies the system has a Solaris-like DTrace and YJIT doesn't support those systems. YJIT_OBJ expands to nothing, and yjit.c isn't compiled. I tested on OmniOS v11 r151034m with: $ ../src/configure --with-out-ext=psych MAKE=gmake AR=ar debugflags=-g $ gmake -j It builds before and after this change. [Bug #18480]
* Reduce duplicate replacementsNobuyoshi Nakada2022-05-301-5/+5
| | | | | | Reduce duplicate replacements so that reflect macros in command lines consitently. So that reflect macros in command lines. Others than `nmake` have no problems with nested expansions.
* Run find in PATH [ci skip]Nobuyoshi Nakada2022-05-251-1/+1
|
* Clean intermediate files for update-deps [ci skip]Nobuyoshi Nakada2022-05-251-0/+1
|
* Clean intermediate object filesNobuyoshi Nakada2022-05-181-0/+1
|
* Verbose mode on libyjit mergeNobuyoshi Nakada2022-05-181-2/+2
|
* Extract YJIT_LIBS directly without copyingNobuyoshi Nakada2022-05-181-2/+1
|
* `AR` does not need the absolute pathNobuyoshi Nakada2022-05-181-5/+6
| | | | | Still use `find` to get rid of potential ARGV limit overflow, since rustc-genrated object file names are mangled and very long.
* Set `target_os` for a7577dbfd3ea53cccf7aaf94208069784ad17791Nobuyoshi Nakada2022-05-171-0/+1
|
* YJIT: Handle spaces in build dir path using find(1) `-exec`Alan Wu2022-04-281-9/+3
| | | | | | | | | | | | | | | | | | | | Previously, we relied on shell word splitting, which leads to passing the wrong arguments when there are white spaces in the path. Avoiding command substitution also makes this script more likely to work under Solaris 10, where `/bin/sh` is not POSIX compliant [1]. (Thanks you, `@znz` for fixing the syntax error in 4210ae2158b545beda908fb29e03d23994f262e3 though!) The hack from c466f270b891962518763ad299f907beac0ebf62 doesn't actually work so this commit reverts it. The shell still needs to parse through all of the code, maybe because make doesn't in fact send newlines to the shell. By the way, we also use the `-exec` option in the `ext/distclean` task. [1]: https://docs.oracle.com/cd/E26505_01/html/816-5165/sh-1.html
* Try to fix error on SolarisKazuhiro NISHIYAMA2022-04-281-1/+1
| | | | | | | | | | | 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) ```
* Work around shell syntax error on SolarisAlan Wu2022-04-271-3/+9
| | | | | | | | 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.
* Rust YJITAlan Wu2022-04-271-1/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* Fix fake.rb RUBY_DESCRIPTION faking for JITsAlan Wu2022-04-111-3/+9
| | | | | | | | | 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.
* Retrieve previously configured macros also other than `extensions`Nobuyoshi Nakada2022-04-071-1/+0
|
* Retrieve configured gems infoNobuyoshi Nakada2022-04-072-3/+3
|
* Bundled gems are expanded under `.bundle/gems` nowNobuyoshi Nakada2022-04-071-1/+1
|
* Load fake.rb at `BTESTRUBY`Nobuyoshi Nakada2022-04-052-2/+3
| | | | | So that `mkmf` checks work from `make run`, and also remove duplicate `$(MINIRUBYOPT)` which is used in `$(MINIRUBY)`.
* Need to reconfigure and rebuild everything when abi.h changedNobuyoshi Nakada2022-03-231-2/+4
|
* exts.mk.tmpl: propagate MINIRUBY to enc.mk even though invoking from exts.mkYuta Saito2022-03-091-1/+1
| | | | | | | | | | 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
* [Feature #18491] Drop support for HP-UXPeter Zhu2022-01-181-1/+0
| | | | | IA64 support was dropped in ticket #15894, so we can drop support for HP-UX.
* Use rb_cObject instead of rb_cDataNobuyoshi Nakada2021-12-311-1/+1
|
generated by cgit v1.2.3 (git 2.39.1) at 2024-06-04 22:06:08 +0000