Yukihiro "Matz" Matsumoto
3cc60d31c6
On 32-bit platforms whose ABI gives 8-byte members 8-byte alignment (xtensa, ARM, MIPS, PowerPC, ...), MRB_NAN_BOXING failed to build with "RVALUE size must be within 5 words" because two structs got padded past the budget: - struct RBreak: had an existing MRB_USE_RBREAK_VALUE_UNION workaround that stores the value as uint32_t[] to avoid forcing 8-byte alignment on the struct, but the gate only enabled it for MRB_NO_BOXING. Extend to NAN_BOXING + 32-bit, with a NAN_BOXING-specific get/set (no separate tt to stash since nan-boxing encodes type in the bits). - struct RArray: MRB_ARY_NO_EMBED was similarly gated to NO_BOXING; embedded mrb_value[] forces 8-byte alignment of the inner union and pads the heap-form layout. Extend the gate to NAN_BOXING + 32-bit. Both gates now name the structural property (32-bit + mrb_value has an 8-byte aligned member) rather than enumerating boxing modes, so adding new boxing modes won't silently miss this class of bug again. i386's System V ABI gives uint64_t only 4-byte alignment, hiding the problem on x86 -m32; -malign-double simulates the strict-alignment ABI that exhibits the failure, and is what was used to verify the fix. Closes #6815, reported by dearblue. Co-authored-by: Claude <noreply@anthropic.com>
mruby
Table of contents
- What is mruby
- How to get mruby
- mruby homepage
- Mailing list
- How to compile, test, and install (mruby and gems)
- Amalgamation (single-file build)
- Building documentation
- How to customize mruby (mrbgems)
- Index of Document
- License
- Note for License
- How to Contribute
- Star History
- Contributors
What is mruby
mruby is the lightweight implementation of the Ruby language complying to (part of) the ISO standard with more recent features provided by Ruby 4.x. Also, its syntax is Ruby 4.x compatible.
You can link and embed mruby within your application. The "mruby" interpreter program and the interactive "mirb" shell are provided as examples. You can also compile Ruby programs into compiled byte code using the "mrbc" compiler. All these tools are located in the "bin" directory. "mrbc" can also generate compiled byte code in a C source file. See the "mrbtest" program under the "test" directory for an example.
This achievement was sponsored by the Regional Innovation Creation R&D Programs of the Ministry of Economy, Trade and Industry of Japan.
How to get mruby
To get mruby, you can download the stable version 4.0.0 from the official mruby GitHub repository or clone the trunk of the mruby source tree with the "git clone" command. You can also install and compile mruby using ruby-install, ruby-build, rvm, conda or Homebrew.
The release candidate version 4.0.0 of mruby can be downloaded via the following URL: https://github.com/mruby/mruby/archive/4.0.0-rc3.zip
The latest development version of mruby can be downloaded via the following URL: https://github.com/mruby/mruby/zipball/master
The trunk of the mruby source tree can be checked out with the following command:
$ git clone https://github.com/mruby/mruby.git
mruby homepage
The URL of the mruby homepage is: https://mruby.org.
Mailing list
We don't have a mailing list, but you can use GitHub issues.
How to compile, test, and install (mruby and gems)
For the simplest case, type
rake all test
See the compile.md file for the detail.
Amalgamation (single-file build)
mruby supports amalgamation, which combines all source files into a single
mruby.c and mruby.h for easy embedding (similar to SQLite).
rake amalgam
Output files are generated in build/host/amalgam/. To use:
gcc -I./build/host/amalgam your_app.c ./build/host/amalgam/mruby.c -o your_app -lm
Building documentation
There are two sets of documentation in mruby: the mruby API (generated by YARD) and C API (Doxygen and Graphviz)
To build both of them, simply go
rake doc
You can also view them in your browser
rake view_api
rake view_capi
How to customize mruby (mrbgems)
mruby contains a package manager called "mrbgems" that you can use to create extensions in C and/or Ruby. For a guide on how to use mrbgems, consult the mrbgems.md file, and for example code, refer to the examples/mrbgems/ folder.
Index of Document
- About the Limitations of mruby
- About Amalgamation (Single-File Build)
- C API Reference
- About the Compile
- About the Debugger with the
mrdbCommand - About GC Arena
- Getting Started with mruby
- About the mruby directory structure
- About Linking with
libmruby - About Memory Allocator Customization and Heap Regions
- About Build-time Configurations
- About the Build-time Library Manager
- ROM Method Tables for Memory-Efficient Method Registration
- About the Symbols
- Internal Implementation / About mruby Architecture
- Internal Implementation / About Value Boxing
- Internal Implementation / About mruby Virtual Machine Instructions
License
mruby is released under the MIT License.
Note for License
mruby has chosen a MIT License due to its permissive license allowing developers to target various environments such as embedded systems. However, the license requires the display of the copyright notice and license information in manuals for instance. Doing so for big projects can be complicated or troublesome. This is why mruby has decided to display "mruby developers" as the copyright name to make it simple conventionally. In the future, mruby might ask you to distribute your new code (that you will commit,) under the MIT License as a member of "mruby developers" but contributors will keep their copyright. (We did not intend for contributors to transfer or waive their copyrights, actual copyright holder name (contributors) will be listed in the AUTHORS file.)
Please ask us if you want to distribute your code under another license.
How to Contribute
To contribute to mruby, please refer to the contribution guidelines and send a pull request to the mruby GitHub repository. By contributing, you grant non-exclusive rights to your code under the MIT License.