[#61822] Plan Developers Meeting Japan April 2014 — Zachary Scott <e@...>

I would like to request developers meeting around April 17 or 18 in this mo=

14 messages 2014/04/03
[#61825] Re: Plan Developers Meeting Japan April 2014 — Urabe Shyouhei <shyouhei@...> 2014/04/03

It's good if we have a meeting then.

[#61826] Re: Plan Developers Meeting Japan April 2014 — Zachary Scott <e@...> 2014/04/03

Regarding openssl issues, I=E2=80=99ve discussed possible meeting time with=

[#61833] Re: Plan Developers Meeting Japan April 2014 — Martin Bo煬et <martin.bosslet@...> 2014/04/03

Hi,

[ruby-core:61809] [ruby-trunk - Bug #9692] [Closed] __builtin_longjmp is called with a value greater than 1 (GCC compilation error)

From: nobu@...
Date: 2014-04-02 08:43:26 UTC
List: ruby-core #61809
Issue #9692 has been updated by Nobuyoshi Nakada.

Status changed from Open to Closed
% Done changed from 0 to 100

Applied in changeset r45503.

----------
configure.in: do not use a variable for longjmp

* configure.in (ac_cv_func___builtin_setjmp): gcc 4.9 disallows a
  variable as the second argument of __builtin_longjmp().
  [ruby-core:61800] [Bug #9692]

----------------------------------------
Bug #9692: __builtin_longjmp is called with a value greater than 1 (GCC com=
pilation error)
https://bugs.ruby-lang.org/issues/9692#change-46044

* Author: Martin Li=C5=A1ka
* Status: Closed
* Priority: Normal
* Assignee:=20
* Category:=20
* Target version:=20
* ruby -v: 2.0.0-p353
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
Hello,
    during testing of LTO on a gentoo machine:
Linux qemubox 3.12.13-gentoo #2 SMP Fri Mar 28 22:30:38 Local time zone mus=
t be set--see zic  x86_64 Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz GenuineIn=
tel GNU/Linux

Configure detects:

~~~
checking for __builtin_setjmp... yes
checking for setjmp type... __builtin_setjmp
~~~

Problem is that ruby calls longjmp with value greater than 1, e.g. `TAG_RAI=
SE` (0x6). With `-flto` compiler proves that `__builtin_longjmp` is always =
called with such a value and following errors are displayed:

~~~
eval.c: In function =E2=80=98rb_jump_tag=E2=80=99:
eval.c:668:5: error: =E2=80=98__builtin_longjmp=E2=80=99 second argument mu=
st be 1
     JUMP_TAG(tag);
     ^
thread.c: In function =E2=80=98rb_threadptr_to_kill=E2=80=99:
thread.c:1887:5: error: =E2=80=98__builtin_longjmp=E2=80=99 second argument=
 must be 1
     TH_JUMP_TAG(th, TAG_FATAL);
     ^
vm.c: In function =E2=80=98vm_exec=E2=80=99:
vm.c:1413:3: error: =E2=80=98__builtin_longjmp=E2=80=99 second argument mus=
t be 1
   JUMP_TAG(state);
   ^
eval.c: In function =E2=80=98setup_exception=E2=80=99:
eval.c:437:34: error: =E2=80=98__builtin_longjmp=E2=80=99 second argument m=
ust be 1
  if (INTERNAL_EXCEPTION_P(mesg)) JUMP_TAG(TAG_FATAL);
                                  ^
eval.c:502:2: error: =E2=80=98__builtin_longjmp=E2=80=99 second argument mu=
st be 1
  JUMP_TAG(TAG_FATAL);
  ^
eval.c: In function =E2=80=98rb_raise_jump=E2=80=99:
eval.c:662:5: error: =E2=80=98__builtin_longjmp=E2=80=99 second argument mu=
st be 1
     JUMP_TAG(TAG_RAISE);
     ^
eval.c: In function =E2=80=98rb_longjmp=E2=80=99:
eval.c:521:5: error: =E2=80=98__builtin_longjmp=E2=80=99 second argument mu=
st be 1
     JUMP_TAG(tag);
     ^
gc.c: In function =E2=80=98rb_memerror=E2=80=99:
gc.c:3417:2: error: =E2=80=98__builtin_longjmp=E2=80=99 second argument mus=
t be 1
  JUMP_TAG(TAG_RAISE);
  ^
~~~

~~~
gcc --version:
gcc (GCC) 4.9.0 20140331 (experimental)
~~~


---Files--------------------------------
ruby-configure-builtin_longjmp.patch (573 Bytes)


--=20
https://bugs.ruby-lang.org/

In This Thread

Prev Next