Shugo MaedaandClaude Fable 5 79d4e720f8 Make locals read after longjmp volatile in more setjmp users
Audit of every EC_PUSH_TAG user, following the LLVM 19 longjmp
rematerialization bug worked around in rb_fiber_start: locals and
arguments that are read on the longjmp path but not modified inside
the tag region are made volatile.  C99 7.13.2.1p3 guarantees such
unmodified locals, but LLVM 17 and 19 have been observed to
reconstruct their values incorrectly after a longjmp (cfp in
rb_iterate0, fiber in rb_fiber_start).  volatile on a parameter may
not be effective (67d0f4821f,
https://bugs.ruby-lang.org/issues/19145), so arguments are copied
into volatile locals instead.

* vm_eval.c (rb_iterate0): cfp is compared against the escaping
  frame after a longjmp; clang 17 at -O1 with -fPIC was observed to
  clobber it during the development of the ifunc invalidation for
  https://bugs.ruby-lang.org/issues/22019.  ec is read next to it to
  rewind the frame and to rethrow.

* eval_error.c (rb_ec_error_print_detailed0): opt and highlight are
  read on the path reached by a longjmp from rb_get_backtrace while
  the other locals of the function are already volatile.

* scheduler.c (rb_fiber_scheduler_unblock, fiber_interrupt): ec and
  saved_interrupt_mask are read after a longjmp to restore
  ec->interrupt_mask; cfp next to them was already volatile.

* eval.c (rb_vrescue2): r_proc and data2 are used when the raise is
  handled.  args is left as is; a va_list cannot portably be
  volatile-qualified and is memory-backed in practice.

* eval.c (rb_protect): pstate is written through after the tag is
  popped.

* eval.c (rb_ec_ensure): ec, e_proc and data2 run the ensure proc
  after a longjmp; a clobbered e_proc would miscall it.

* vm_eval.c (vm_catch_protect): stateptr is written through after
  the pop.  tag has its address taken and stays in memory.

* vm_trace.c (exec_hooks_protected): ec and list are passed to
  exec_hooks_postcheck after the pop.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-23 10:37:13 +09:00
…
…
2026-07-16 09:47:27 +09:00
2026-07-15 18:42:29 +09:00
2026-07-15 15:43:28 +02:00
2026-07-20 08:22:03 +00:00
2026-07-22 12:37:58 +09:00
…
2026-07-22 13:20:49 -04:00
2026-07-13 14:25:10 +09:00
2026-07-22 14:29:08 -04:00
…
2026-03-06 14:02:00 +09:00
2025-04-09 19:13:58 +09:00
2026-05-18 08:58:32 +03:00
2026-07-15 15:43:28 +02:00
2026-07-17 15:13:13 +09:00
2025-05-11 23:32:50 +09:00
2025-05-11 23:32:50 +09:00
…
…
2026-06-29 09:14:47 +09:00
2026-07-22 23:52:01 +02:00
2026-04-09 13:24:09 +01:00
2024-09-08 23:40:18 +09:00
…
2026-01-31 17:45:03 -05:00
2024-04-27 21:55:28 +09:00
2026-07-15 13:13:07 +02:00
2026-07-10 15:33:42 +09:00
…
2026-07-16 15:13:09 +09:00
2026-07-15 15:21:01 +09:00
2026-06-09 15:11:05 +09:00
2026-06-16 10:28:33 +02:00
2025-09-06 07:17:52 +09:00
2025-06-12 09:30:09 +02:00
2025-08-30 22:41:23 +09:00
2025-01-09 19:24:27 +09:00
2025-01-30 18:19:53 +09:00
2025-12-15 17:28:35 -05:00
2026-07-15 15:43:28 +02:00
2026-03-16 15:04:38 +01:00
2026-07-13 04:19:52 +09:00
2026-01-15 17:20:34 +09:00
2026-07-07 20:59:49 +09:00
2026-07-15 15:21:01 +09:00
2026-07-22 23:52:01 +02:00
2026-07-10 14:38:52 +09:00
2026-07-17 13:26:25 +09:00
2026-07-22 23:52:01 +02:00
2026-07-07 09:21:13 +02:00
2026-07-22 23:52:01 +02:00
2026-07-21 11:00:57 -04:00
2026-07-21 11:00:57 -04:00
…
…
2024-10-20 19:33:21 +09:00
2025-07-28 12:22:42 +02:00
2026-07-15 13:35:36 -07:00
…
…
2026-07-15 15:21:01 +09:00
2026-07-15 13:28:39 +09:00
2025-12-10 10:23:37 +09:00
2026-07-22 14:29:08 -04:00
2026-07-15 13:28:39 +09:00
2026-05-08 11:27:05 -07:00
2026-07-15 13:28:39 +09:00
2026-07-15 15:43:28 +02:00

Actions Status: MinGW Actions Status: Ubuntu Actions Status: Windows Travis Status

日本語

What is Ruby?

Ruby is an interpreted object-oriented programming language often used for web development. It also offers many scripting features to process plain text and serialized files, or manage system tasks. It is simple, straightforward, and extensible.

Features of Ruby

  • Simple Syntax
  • Normal Object-oriented Features (e.g. class, method calls)
  • Advanced Object-oriented Features (e.g. mix-in, singleton-method)
  • Operator Overloading
  • Exception Handling
  • Iterators and Closures
  • Garbage Collection
  • Dynamic Loading of Object Files (on some architectures)
  • Highly Portable (works on many Unix-like/POSIX compatible platforms as well as Windows, macOS, etc.) cf. https://docs.ruby-lang.org/en/master/maintainers_md.html#label-Platform+Maintainers

How to get Ruby

For a complete list of ways to install Ruby, including using third-party tools like rvm, see:

https://www.ruby-lang.org/en/downloads/

You can download release packages and the snapshot of the repository. If you want to download whole versions of Ruby, please visit https://www.ruby-lang.org/en/downloads/releases/.

Download with Git

The mirror of the Ruby source tree can be checked out with the following command:

$ git clone https://github.com/ruby/ruby.git

There are some other branches under development. Try the following command to see the list of branches:

$ git ls-remote https://github.com/ruby/ruby.git

You may also want to use https://git.ruby-lang.org/ruby.git (actual master of Ruby source) if you are a committer.

How to build

See Building Ruby

Ruby home page

https://www.ruby-lang.org/

Documentation

Mailing list

There is a mailing list to discuss Ruby. To subscribe to this list, please send the following phrase:

join

in the mail subject (not body) to the address ruby-talk-request@ml.ruby-lang.org.

Copying

See the file COPYING.

Feedback

Questions about the Ruby language can be asked on the Ruby-Talk mailing list or on websites like https://stackoverflow.com.

Bugs should be reported at https://bugs.ruby-lang.org. Read "Reporting Issues" for more information.

Contributing

See "Contributing to Ruby", which includes setup and build instructions.

The Author

Ruby was originally designed and developed by Yukihiro Matsumoto (Matz) in 1995.

matz@ruby-lang.org

Languages
Ruby 57.2%
C 29.4%
Rust 8%
C++ 2.6%
Yacc 0.9%
Other 1.8%