[#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:90588] [Ruby trunk Bug#15425] Store MJIT header into Ruby versioned directory.
From:
v.ondruch@...
Date:
2018-12-17 15:08:52 UTC
List:
ruby-core #90588
Issue #15425 has been updated by vo.x (Vit Ondruch).
I am using `--with-rubyhdrdir=/usr/include --with-rubyarchhdrdir=/usr/include --enable-multiarch` configuration options. This is the output:
~~~
$ tree
.
`-- ruby-2.6.0
|-- ruby
| |-- backward
| | |-- classext.h
| | |-- rubyio.h
| | |-- rubysig.h
| | |-- st.h
| | `-- util.h
| |-- backward.h
| |-- debug.h
| |-- defines.h
| |-- digest.h
| |-- encoding.h
| |-- intern.h
| |-- io.h
| |-- missing.h
| |-- onigmo.h
| |-- oniguruma.h
| |-- re.h
| |-- regex.h
| |-- ruby.h
| |-- st.h
| |-- subst.h
| |-- thread.h
| |-- thread_native.h
| |-- util.h
| |-- version.h
| `-- vm.h
|-- ruby-2.6.0
| `-- x86_64-linux
|-- ruby.h
`-- x86_64-linux
|-- rb_mjit_min_header-2.6.0.h
`-- ruby
`-- config.h
7 directories, 28 files
~~~
Different headers respect the configuration differently. The header should be probably placed on the same location as "config.h" for consistency. The `ruby-2.6.0/ruby-2.6.0/x86_64-linux` should not be created at all.
----------------------------------------
Bug #15425: Store MJIT header into Ruby versioned directory.
https://bugs.ruby-lang.org/issues/15425#change-75743
* Author: vo.x (Vit Ondruch)
* Status: Feedback
* Priority: Normal
* Assignee:
* Target version:
* ruby -v: ruby 2.6.0rc2 (2018-12-15 trunk 66408) [x86_64-linux]
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN
----------------------------------------
This is a followup of #15391 which fixes JIT to respect the configuration options. However, I still wonder, why the file is versioned and why it is not stored in the versioned directory alongside all other internal Ruby headers. I believe, that while it now respects the header configuration flags, it still does not respect options such as "--with-ruby-version"
--
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>