[#64210] Asking for clarification for exception handling usage — Rodrigo Rosenfeld Rosas <rr.rosas@...>
I've created a ticket for that but didn't get any feedback so I decided
[#64517] Fw: Re: Ruby and Rails to become Apache Incubator Project — Tetsuya Kitahata <kitahata@99.alumni.u-tokyo.ac.jp>
What do you think? >> Ruby developers
What benefits are there to this? I have a feeling that adding unnecessary
On Sat, 23 Aug 2014 22:43:46 -0700
Here I am a Japanese. Before moving anywhere else answer to our question first: what benefits?
tax issue with each other.
Forgot to assert my opinions:
[#64614] cowspace (work-in-progress) — Eric Wong <normalperson@...>
Hi all, I started working on a cowspace branch. Based on the mspace API
[#64615] [ruby-trunk - Feature #10181] [Open] New method File.openat() — oss-ruby-lang@...
Issue #10181 has been reported by Technorama Ltd..
I like this feature.
On 08/28/2014 02:53 PM, Eric Wong wrote:
Joel VanderWerf <joelvanderwerf@gmail.com> wrote:
On 08/29/2014 12:55 AM, Eric Wong wrote:
Joel VanderWerf <joelvanderwerf@gmail.com> wrote:
[#64627] [ruby-trunk - Feature #10182] [PATCH] string.c: move frozen_strings table to rb_vm_t — ko1@...
Issue #10182 has been updated by Koichi Sasada.
[#64671] Fwd: [ruby-changes:35240] normal:r47322 (trunk): symbol.c (rb_sym2id): do not return garbage object — SASADA Koichi <ko1@...>
Why this fix solve your problem?
(2014/08/30 8:50), SASADA Koichi wrote:
SASADA Koichi <ko1@atdot.net> wrote:
Eric Wong <normalperson@yhbt.net> wrote:
(2014/08/31 0:18), Eric Wong wrote:
[ruby-core:64548] [ruby-trunk - Bug #9692] __builtin_longjmp is called with a value greater than 1 (GCC compilation error)
Issue #9692 has been updated by Tomoyuki Chikanaga.
Backport changed from 2.0.0: REQUIRED, 2.1: REQUIRED to 2.0.0: REQUIRED, 2.1: DONE
r45503, r45504, r45508, r45509 and r47275 were backported into `ruby_2_1` branch at r47276.
----------------------------------------
Bug #9692: __builtin_longjmp is called with a value greater than 1 (GCC compilation error)
https://bugs.ruby-lang.org/issues/9692#change-48476
* Author: Martin Liška
* Status: Closed
* Priority: Normal
* Assignee:
* Category:
* Target version:
* ruby -v: 2.0.0-p353
* Backport: 2.0.0: REQUIRED, 2.1: DONE
----------------------------------------
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 must be set--see zic x86_64 Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz GenuineIntel 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_RAISE` (0x6). With `-flto` compiler proves that `__builtin_longjmp` is always called with such a value and following errors are displayed:
~~~
eval.c: In function ‘rb_jump_tag’:
eval.c:668:5: error: ‘__builtin_longjmp’ second argument must be 1
JUMP_TAG(tag);
^
thread.c: In function ‘rb_threadptr_to_kill’:
thread.c:1887:5: error: ‘__builtin_longjmp’ second argument must be 1
TH_JUMP_TAG(th, TAG_FATAL);
^
vm.c: In function ‘vm_exec’:
vm.c:1413:3: error: ‘__builtin_longjmp’ second argument must be 1
JUMP_TAG(state);
^
eval.c: In function ‘setup_exception’:
eval.c:437:34: error: ‘__builtin_longjmp’ second argument must be 1
if (INTERNAL_EXCEPTION_P(mesg)) JUMP_TAG(TAG_FATAL);
^
eval.c:502:2: error: ‘__builtin_longjmp’ second argument must be 1
JUMP_TAG(TAG_FATAL);
^
eval.c: In function ‘rb_raise_jump’:
eval.c:662:5: error: ‘__builtin_longjmp’ second argument must be 1
JUMP_TAG(TAG_RAISE);
^
eval.c: In function ‘rb_longjmp’:
eval.c:521:5: error: ‘__builtin_longjmp’ second argument must be 1
JUMP_TAG(tag);
^
gc.c: In function ‘rb_memerror’:
gc.c:3417:2: error: ‘__builtin_longjmp’ second argument must be 1
JUMP_TAG(TAG_RAISE);
^
~~~
~~~
gcc --version:
gcc (GCC) 4.9.0 20140331 (experimental)
~~~
---Files--------------------------------
ruby-configure-builtin_longjmp.patch (573 Bytes)
--
https://bugs.ruby-lang.org/