summaryrefslogtreecommitdiff
path: root/tool/m4
AgeCommit message (Collapse)Author
2024-12-22Support RUBY_MODULAR_GC with LOAD_RELATIVENobuyoshi Nakada
Notes: Merged: https://github.com/ruby/ruby/pull/12428
2024-12-05Standardize on the name "modular GC"Peter Zhu
We have name fragmentation for this feature, including "shared GC", "modular GC", and "external GC". This commit standardizes the feature name to "modular GC" and the implementation to "GC library". Notes: Merged: https://github.com/ruby/ruby/pull/12261
2024-11-09Add integer overflow check macros for add/sub as well as mulNobuyoshi Nakada
Notes: Merged: https://github.com/ruby/ruby/pull/12034
2024-07-26Error when --with-shared-gc doesn't specify a directoryPeter Zhu
Notes: Merged: https://github.com/ruby/ruby/pull/11248
2024-07-09Fix grammar of ruby_shared_gc.m4Peter Zhu
2024-07-08Add make target shared-gcPeter Zhu
Allows building shared GC using `make shared-gc SHARED_GC=gc_impl`
2024-07-05Change external GC to use directory at configurePeter Zhu
This commit changes the external GC API to use `--with-shared-gc=DIR` at configure time with a directory of the external GC and uses `RUBY_GC_LIBRARY` environment variable to load the external GC at runtime.
2024-06-24No longer needs `sigsetjmp`Nobuyoshi Nakada
Since signal handlers just set flag and return now, `sigsetjmp` and `siglongjmp` will not be needed.
2024-06-11Extract hardening CFLAGS to a special $hardenflags variableKJ Tsanaktsidis
This changes the automatic detection of -fstack-protector, -D_FORTIFY_SOURCE, and -mbranch-protection to write to $hardenflags instead of $XCFLAGS. The definition of $cflags is changed to "$hardenflags $orig_cflags $optflags $debugflags $warnflags" to match. Furthermore, these flags are _prepended_ to $hardenflags, rather than appended. The implications of doing this are as follows: * If a CRuby builder specifies cflags="-mbranch-protection=foobar" at the ./configure script, and the configure script detects that -mbranch-protection=pac-ret is accepted, then GCC will be invoked as "gcc -mbranch-protection=pac-ret -mbranch-protection=foobar". Since the last flags take precedence, that means that user-supplied values of these flags in $cflags will take priority. * Likewise, if a CRuby builder explicitly specifies "hardenflags=-mbranch-protection=foobar", because we _prepend_ to $hardenflags in our autoconf script, we will still invoke GCC as "gcc -mbranch-protection=pac-ret -mbranch-protection=foobar". * If a CRuby builder specifies CFLAGS="..." at the configure line, automatic detection of hardening flags is ignored as before. * C extensions will _also_ be built with hardening flags now as well (this was not the case by default before because the detected flags went into $XCFLAGS). Additionally, as part of this work, I changed how the detection of PAC/BTI in Context.S works. Rather than appending the autodetected option to ASFLAGS, we simply compile a set of test programs with the actual CFLAGS in use to determine what PAC/BTI settings were actually chosen by the builder. Context.S is made aware of these choices through some custom macros. The result of this work is that: * Ruby will continue to choose some sensible defaults for hardening options for the C compiler * Distributors are able to specify CFLAGS that are consistent with their distribution and override these defaults * Context.S will react to whatever -mbranch-protection is actually in use, not what was autodetected * Extensions get built with hardening flags too. [Bug #20154] [Bug #20520]
2024-05-30RUBY_CHECK_HEADER didn't define HAVE_{header-file} (#10876)Sorah Fukumori
--with-gmp is not working at all because HAVE_GMP_H was missing since 18eaf0be90. [Bug #20515] bug: https://bugs.ruby-lang.org/issues/20515 follow-up: https://bugs.ruby-lang.org/issues/20494 follow-up: 18eaf0be905e3e251423b42d6f4e56b7cae1bc3b follow-up: https://github.com/ruby/ruby/pull/10805
2024-05-20[Bug #20494] Search non-default directories for GMPNobuyoshi Nakada
Co-Authored-by: lish82 (Hiroki Katagiri)
2024-04-15Add --with-shared-gc build flagMatt Valentine-House
2024-04-02[DOC] Fix wheather -> whether typos in configure.Matt Valentine-House
2024-02-06[wasm] tool/m4/ruby_wasm_tools.m4: Add default value for OBJCOPYYuta Saito
The tool is used to build shared libraries but system installed tools usually don't support WebAssembly, so use WASI SDK's tools by default.
2023-12-27[Bug #20088] Fix ARCH_FLAG for cross compilingNobuyoshi Nakada
2023-12-15Ignore the spcial case of target_cpuNobuyoshi Nakada
On Windows, x86_64 is called as x64.
2023-12-15Fix `ARCH_FLAG` when cross-compiling on macOSNobuyoshi Nakada
2023-12-15Fix `ARCH_FLAG` when `--with-arch` with single CPUNobuyoshi Nakada
2023-10-21Strip universal_archnamesNobuyoshi Nakada
2023-02-26Fix autoconf RUBY_STACK_GROW_DIRECTION on ARM devicesBen Hamilton
Notes: Merged: https://github.com/ruby/ruby/pull/7373
2022-12-21tool/m4/ruby_wasm_tools.m4: force passing WASI_SDK_PATH when building for wasiYuta Saito
Make the WASI_SDK_PATH variable mandatory when building for wasi host. This requirement prevents developers from being stuck due to unfriendly configuration's error message. Notes: Merged: https://github.com/ruby/ruby/pull/5464
2022-10-19Fix and improve coroutines for Darwin (macOS) ppc/ppc64. (#5975)Sergey Fedorov
Notes: Merged-By: ioquatix <samuel@codeotaku.com>
2022-07-07Fallback `mkdir_p` to `as_mkdir_p`Nobuyoshi Nakada
Assume `mkdir -p` to be race-free on recent systems. And we do not provide install-sh anyway.
2022-05-10Honor --with-thread option to enable pthreadNobuyoshi Nakada
2022-03-30Fix locations of the second argumentNobuyoshi Nakada
2022-03-28Fix a missing commaNobuyoshi Nakada
2022-03-28Use m4 comments outside macros in m4 filesNobuyoshi Nakada
2022-03-28Extract RUBY_REQUIRE_FUNCSNobuyoshi Nakada
2022-02-19RUBY_REPLACE_TYPE: check if the target type is a pointerNobuyoshi Nakada
Notes: Merged: https://github.com/ruby/ruby/pull/5574
2022-01-23Reuse the default `AC_LANG_PROGRAM(C)` definitionNobuyoshi Nakada
2022-01-22Override `AC_C_PROGRAM` on old autoconfNobuyoshi Nakada
Autoconf 2.69 fails to detect `-Werror=old-style-definition` due to the old style definition of `main`.
2022-01-19[wasm] add no thread variant for freestanding environmentYuta Saito
This implementation does nothing around preemptive context switching because there is no native thread. Notes: Merged: https://github.com/ruby/ruby/pull/5407
2022-01-19[wasm] add asyncify based setjmp, fiber, register scan emulationYuta Saito
configure.ac: setup build tools and register objects main.c: wrap main with rb_wasm_rt_start to handle asyncify unwinds tool/m4/ruby_wasm_tools.m4: setup default command based on WASI_SDK_PATH environment variable. checks wasm-opt which is used for asyncify. tool/wasm-clangw wasm/wasm-opt: a clang wrapper which replaces real wasm-opt with do-nothing wasm-opt to avoid misoptimization before asyncify. asyncify is performed at POSTLINK, but clang linker driver tries to run optimization by wasm-opt unconditionally. inlining pass at wasm level breaks asyncify's assumption, so should not optimize before POSTLIK. wasm/GNUmakefile.in: wasm specific rules to compile objects Notes: Merged: https://github.com/ruby/ruby/pull/5407
2021-10-30Allow the thread-model to be switched by configure optionYuta Saito
This change adds --with-thread=IMPL option to the configure. If not supplied, default implementation for each platform will be used. Notes: Merged: https://github.com/ruby/ruby/pull/5043
2021-10-30Select including thread impl file at config timeYuta Saito
Notes: Merged: https://github.com/ruby/ruby/pull/5043
2021-10-30Split thread-model config into another ac fileYuta Saito
This is a first step to allow the thread-model implementation to be switched by configure's option Notes: Merged: https://github.com/ruby/ruby/pull/5043
2021-10-01Checks for CPU specific header on universal buildNobuyoshi Nakada
Notes: Merged: https://github.com/ruby/ruby/pull/4921
2021-10-01Prefer `printf` like the recent autoconfNobuyoshi Nakada
Notes: Merged: https://github.com/ruby/ruby/pull/4921
2021-07-06Try "so" attribute if "smso" is not foundNobuyoshi Nakada
2021-04-17Remove comments in tool/m4 from the generated configureNobuyoshi Nakada
2021-01-22Keep ARCH_OPTION for arm64Nobuyoshi Nakada
2021-01-18Update for autoconf 2.70Nobuyoshi Nakada
Notes: Merged: https://github.com/ruby/ruby/pull/4086
2020-12-13Fixed RUBY_RM_RECURSIVE when autoconf met the required versionNobuyoshi Nakada
Before 9189cf5793cd527a86b711d15d5fd0633ec082e1 the result of `m4_version_compare` was compared to -1, however the `$2` of `m4_version_prereq` has different meaning and is expanded when the required version met.
2020-06-30Extract correct processor name for ARM64 MacsSamuel Giddins
Notes: Merged: https://github.com/ruby/ruby/pull/3272
2020-04-08Merge pull request #2991 from shyouhei/ruby.h卜部昌平
Split ruby.h Notes: Merged-By: shyouhei <shyouhei@ruby-lang.org>
2020-04-05Revert "Moved aclocal.m4 to macro directory"Nobuyoshi Nakada
This reverts commit 4a6571dbc14ee4e88c12cd9931f7695077a3ee6e, because chkbuild does not follow.
2020-04-05Moved aclocal.m4 to macro directoryNobuyoshi Nakada
Notes: Merged: https://github.com/ruby/ruby/pull/3003
2020-02-06do not assume GCC for __builtin_setjmp卜部昌平
Namely recent Sun C compiler has this function, and is not a GCC. Meanwhile the code without RUBY_JMP_BUF assumes GCC. We have to define the macro when we detect __builtin_setjmp for non-GCC compilers. Notes: Merged: https://github.com/ruby/ruby/pull/2885
2019-09-21typedef rb_jmpbuf_t to void *[5] if __builtin_setjmp is usedFangrui Song
The built-in version operates on a buffer of 5 words, much smaller than the size of jmp_buf defined in libc. Note, powerpc requires 5 words, while arm and x86_64 just require 3. Notes: Merged: https://github.com/ruby/ruby/pull/2471
2019-06-19Remove IA64 support.Samuel Williams
generated by cgit v1.2.3 (git 2.25.1) at 2026-01-17 00:13:56 +0000