summaryrefslogtreecommitdiff
path: root/template
Commit message (Collapse)AuthorAgeFilesLines
...
* 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
|
* Prepare for removing RubyVM::JIT (#5262)Takashi Kokubun2021-12-131-1/+1
|
* Rename --jit to --mjit (#5248)Takashi Kokubun2021-12-131-1/+1
| | | | | | | | | | | | | | | * 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
* Remove unversioned phony target for pkgconfig file [Bug #18374]Nobuyoshi Nakada2021-12-041-1/+0
| | | | | It results in a circular dependency when `--with-ruby-pc=ruby.pc` is given. [ci skip]
* Update URL about DTrace static library glommed obj [ci skip]Naohisa Goto2021-11-171-1/+1
| | | | | | | | 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.
* [Feature #18290] Remove all usages of rb_gc_force_recyclePeter Zhu2021-11-081-3/+0
| | | | | This commit removes usages of rb_gc_force_recycle since it is a burden to maintain and makes changes to the GC difficult.
* Remove the scraperAaron Patterson2021-10-201-3/+1
| | | | | Now that we're using the jit function entry point, we don't need the scraper. Thank you for your service, scraper. ❤️
* Remove some MicroJIT vestigesAaron Patterson2021-10-201-2/+2
| | | | Just happened to run across this, so lets fix them
* Yet Another Ruby JIT!Jose Narvaez2021-10-201-1/+1
| | | | Renaming uJIT to YJIT. AKA s/ujit/yjit/g.
* Refactor uJIT code into more files for readabilityMaxime Chevalier-Boisvert2021-10-201-1/+1
|
* Refactor ujit_examples.h generator. Remove dwarfdump dependencyAlan Wu2021-10-201-1/+3
|
* Add the dependency of GNUmakefile itself [ci skip]Nobuyoshi Nakada2021-10-061-0/+2
|
* include/ruby/encoding.h: convert macros into inline functions卜部昌平2021-10-051-0/+1
| | | | Less macros == huge win.
* Stop building extension gems for nowNobuyoshi Nakada2021-10-041-1/+1
| | | | | Extension gems will be installed by the installed standard libraries.
* Ripper source on mswinNobuyoshi Nakada2021-09-211-0/+1
| | | | | * Get rid of command substitution for cmd.exe. * Separate RM1 command to remove single file sans directory.
* template/Doxyfile.tmpl: modernise卜部昌平2021-09-151-112/+138
| | | | applied doxygen -g for Doxygen 1.9.3.
* template/Doxyfile.tmpl: EXTRACT_ALL=NO卜部昌平2021-09-101-1/+1
| | | | | | 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]
* template/Doxyfile.tmpl: EXTRACT_STATIC: YES [Bugs #14037]sonots2021-09-101-1/+1
| | | | | | | | | 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]
* template/Doxyfile.tmpl: rethink about exclusions卜部昌平2021-09-101-3/+1
| | | | | | | 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]
* include/ruby/io.h: add doxyen卜部昌平2021-09-101-0/+1
| | | | Must not be a bad idea to improve documents. [ci skip]
* postscript about rb_mutex_sleep卜部昌平2021-09-101-0/+1
| | | | Asked ko1 about the design. [ci skip]
* include/ruby/internal/fl_type.h: add doxygen卜部昌平2021-09-101-0/+2
| | | | Must not be a bad idea to improve documents. [ci skip]
* include/ruby/internal/rgengc.h: add dosygen卜部昌平2021-09-101-0/+1
| | | | Must not be a bad idea to improve documents. [ci skip]
* include/ruby/internal/value_type.h: add doxygen卜部昌平2021-09-101-0/+1
| | | | Must not be a bad idea to improve documents. [ci skip]
View Lorry Controller Status