[Bug 206110] lang/ruby22: fix setjmp clobbered variables (using clang 3.8.0 and optimizing for 'high' CPUs)

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206110

            Bug ID: 206110
           Summary: lang/ruby22: fix setjmp clobbered variables (using
                    clang 3.8.0 and optimizing for 'high' CPUs)
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: ruby at FreeBSD.org
          Reporter: dim at FreeBSD.org
             Flags: maintainer-feedback?(ruby at FreeBSD.org)
          Assignee: ruby at FreeBSD.org

Created attachment 165370
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=165370&action=edit
Mark several variables volatile so they won't have undefined state after
setjmp()

During my preparations for bug 206074 (exp-run for clang 3.8.0), I noticed that
lang/ruby22 would sometimes crash during the build.  Specifically, on i386,
with CPUTYPE=ivybridge, you would get segfaults in miniruby.

It turns out these are because there are several places in ruby where setjmp()
is used, and where not all variables accessed after setjmp() are marked
volatile.  This can cause them to have undefined state.

Fix this by marking several variables in different functions volatile.

These patches were obtained from NetBSD pkgsrc, thanks to Jörg Sonnenberger for
the hint.

-- 
You are receiving this mail because:
You are the assignee for the bug.