[#90399] [Ruby trunk Feature#14813] [PATCH] gc.c: make gc_enter+gc_exit pairs dtrace probes, too — ko1@...
Issue #14813 has been updated by ko1 (Koichi Sasada).
3 messages
2018/12/10
[#90417] [Ruby trunk Bug#15398] TestThread#test_signal_at_join fails on FreeBSD — naruse@...
Issue #15398 has been reported by naruse (Yui NARUSE).
4 messages
2018/12/11
[#90423] Re: [Ruby trunk Bug#15398] TestThread#test_signal_at_join fails on FreeBSD
— Eric Wong <normalperson@...>
2018/12/11
naruse@airemix.jp wrote:
[#90519] Spoofing warnings for mail from bugs.ruby-lang.org — Charles Oliver Nutter <headius@...>
I'm getting a spoofing warning for emails sent from bugs.ruby-lang.org when
4 messages
2018/12/13
[#90522] Re: Spoofing warnings for mail from bugs.ruby-lang.org
— Eric Wong <normalperson@...>
2018/12/13
Charles Oliver Nutter <headius@headius.com> wrote:
[#90533] [Ruby trunk Feature#15413] unmarkable C stack (3rd stack) — normalperson@...
Issue #15413 has been reported by normalperson (Eric Wong).
3 messages
2018/12/14
[#90581] [Ruby trunk Bug#15424] Ruby 2.6.0rc1 & 2.6.0rc2 mutex exception — mat999@...
Issue #15424 has been reported by splitice (Mathew Heard).
3 messages
2018/12/17
[#90595] [Ruby trunk Bug#15430] test_fork_while_parent_locked is failing status on Ruby CI — hsbt@...
Issue #15430 has been reported by hsbt (Hiroshi SHIBATA).
3 messages
2018/12/18
[#90614] [Ruby trunk Bug#15430][Assigned] test_fork_while_parent_locked is failing status on Ruby CI — hsbt@...
Issue #15430 has been updated by hsbt (Hiroshi SHIBATA).
4 messages
2018/12/19
[#90630] Re: [Ruby trunk Bug#15430][Assigned] test_fork_while_parent_locked is failing status on Ruby CI
— Eric Wong <normalperson@...>
2018/12/20
> It still exists. https://rubyci.org/logs/rubyci.s3.amazonaws.com/centos7/ruby-trunk/log/20181218T230003Z.fail.html.gz
[#90820] Re: [ruby-cvs:73697] k0kubun:r66593 (trunk): accept_nonblock_spec.rb: skip spurious failure — Eric Wong <normalperson@...>
k0kubun@ruby-lang.org wrote:
3 messages
2018/12/30
[ruby-core:90756] [Ruby trunk Misc#15474] Running Rails with jit
From:
shevegen@...
Date:
2018-12-27 22:29:44 UTC
List:
ruby-core #90756
Issue #15474 has been updated by shevegen (Robert A. Heiler).
There is some documentation at:
https://bugs.ruby-lang.org/projects/ruby/wiki/MJIT#Basic-usage
I believe Takashi and others may update that page every now and then.
To the suggestion of a new environment variable:
- I have no particular pro or con opinion; to me it seems fine but I think this
has to be decided by Takashi, matz, the ruby core team etc...
If I understood you correctly you refer to RUBY_JIT as an additional option to
RUBYOPT, right? Again, I have no preference, I just want to make the proposal
itself more accurate when possible. (It may help the ruby core team decide
on the proposal; I assume it may be that RUBYOPT might suffice.)
The example given on the wiki-page is this by the way:
RUBYOPT="--jit"
I think people may not easily find the page as of yet. I have bookmarked it
locally so that I can find the page easily and not forget it. :)
----------------------------------------
Misc #15474: Running Rails with jit
https://bugs.ruby-lang.org/issues/15474#change-75929
* Author: foonlyboy (Eike Dierks)
* Status: Open
* Priority: Normal
* Assignee:
----------------------------------------
I have installed ruby-2.6.0
I want to try to run my rails app with the jit.
How can this be done?
I should try env RUBY_OPTS='--jit'
Is this the way the go?
The jit ist experimental, but promising,
so we need to try it wherever we can.
there needs to be a clear documentation,
how to enable or disable jit
I'd like to enable jit by default,
when running 2.6.0
running 2.5.3 with --jit gives:
/opt/local/bin/ruby --jit -e 'puts "hello world"'
/opt/local/bin/ruby: invalid option --jit (-h will show valid options) (RuntimeError)
I'd like to suggest a new env: RUBY_JIT
which should only be respected by ruby >= 2.6.0
~eike
--
https://bugs.ruby-lang.org/
Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>