ruby.git/bootstraptest, branch ruby_2_7 The Ruby Programming Language merge revision(s) 21d8e6924844d592ff2d5a2e7309457eb92e66f6: 2020-07-09T11:54:28+00:00 nagachika nagachika@ruby-lang.org 2020-07-09T11:54:28+00:00 6c22070408f9729621712190bfc8460e5eebcb03 disable to show the maximum number of threads. On Deiban 9 environment, the thread tests failed and this maximum threads information can finish up the machine resources. To check it, I turned-off showing this information. 
	disable to show the maximum number of threads.

	On Deiban 9 environment, the thread tests failed and
	this maximum threads information can finish up the machine
	resources. To check it, I turned-off showing this information.
Show the failed message too 2019-12-12T14:26:35+00:00 Nobuyoshi Nakada nobu@ruby-lang.org 2019-12-12T14:26:29+00:00 93b27c69cc65b5019df061bb8fefaa097bf8a33d 






Show the failed message
2019-12-11T05:27:21+00:00

Nobuyoshi Nakada
nobu@ruby-lang.org

2019-12-11T05:27:21+00:00

0afee4d80355dd03f0dfefe6120e2e1808d9cb50












Use a monotonically increasing number for object_id
2019-11-07T17:31:07+00:00

John Hawthorn
john@hawthorn.email

2019-11-01T00:21:01+00:00

b99833baec2e567e38758f4fd017c90c7ce57d75

This changes object_id from being based on the objects location in
memory (or a nearby memory location in the case of a conflict) to be
based on an always increasing number.

This number is a Ruby Integer which allows it to overflow the size of a
pointer without issue (very unlikely to happen in real programs
especially on 64-bit, but a nice guarantee).

This changes obj_to_id_tbl and id_to_obj_tbl to both be maps of Ruby
objects to Ruby objects (previously they were Ruby object to C integer)
which simplifies updating them after compaction as we can run them
through gc_update_table_refs.

Co-authored-by: Aaron Patterson <tenderlove@ruby-lang.org>





This changes object_id from being based on the objects location in
memory (or a nearby memory location in the case of a conflict) to be
based on an always increasing number.

This number is a Ruby Integer which allows it to overflow the size of a
pointer without issue (very unlikely to happen in real programs
especially on 64-bit, but a nice guarantee).

This changes obj_to_id_tbl and id_to_obj_tbl to both be maps of Ruby
objects to Ruby objects (previously they were Ruby object to C integer)
which simplifies updating them after compaction as we can run them
through gc_update_table_refs.

Co-authored-by: Aaron Patterson <tenderlove@ruby-lang.org>







Revert "Use a monotonically increasing number for object_id"
2019-11-06T23:12:28+00:00

Aaron Patterson
tenderlove@ruby-lang.org

2019-11-06T23:12:28+00:00

e58814d150b0652f5e11958b36b85d977fdd0426

This reverts commit bd2b314a05ae9192b3143e1e678a37c370d8a9ce.





This reverts commit bd2b314a05ae9192b3143e1e678a37c370d8a9ce.







Use a monotonically increasing number for object_id
2019-11-06T22:59:53+00:00

John Hawthorn
john@hawthorn.email

2019-11-01T00:21:01+00:00

bd2b314a05ae9192b3143e1e678a37c370d8a9ce

This changes object_id from being based on the objects location in
memory (or a nearby memory location in the case of a conflict) to be
based on an always increasing number.

This number is a Ruby Integer which allows it to overflow the size of a
pointer without issue (very unlikely to happen in real programs
especially on 64-bit, but a nice guarantee).

This changes obj_to_id_tbl and id_to_obj_tbl to both be maps of Ruby
objects to Ruby objects (previously they were Ruby object to C integer)
which simplifies updating them after compaction as we can run them
through gc_update_table_refs.

Co-authored-by: Aaron Patterson <tenderlove@ruby-lang.org>





This changes object_id from being based on the objects location in
memory (or a nearby memory location in the case of a conflict) to be
based on an always increasing number.

This number is a Ruby Integer which allows it to overflow the size of a
pointer without issue (very unlikely to happen in real programs
especially on 64-bit, but a nice guarantee).

This changes obj_to_id_tbl and id_to_obj_tbl to both be maps of Ruby
objects to Ruby objects (previously they were Ruby object to C integer)
which simplifies updating them after compaction as we can run them
through gc_update_table_refs.

Co-authored-by: Aaron Patterson <tenderlove@ruby-lang.org>







Relaxed tests for CPDEBUG mode
2019-10-22T16:05:52+00:00

Nobuyoshi Nakada
nobu@ruby-lang.org

2019-10-22T16:05:14+00:00

801a11d0ab3e1d387b5aaed92d1965fbdf675780












fix memory corruption in old GCC
2019-10-09T15:13:30+00:00

卜部昌平
shyouhei@ruby-lang.org

2019-10-09T15:10:14+00:00

9b919885a08d6cf3c68cb1bce992feb43a8fad0c

This typo introduced memory corruption when __builtin_add_overflow
is not available but uint128_t is.  GCC before 5 are one of such
situatins.

See also https://rubyci.org/logs/rubyci.s3.amazonaws.com/opensuseleap/ruby-master/log/20191009T120004Z.log.html.gz





This typo introduced memory corruption when __builtin_add_overflow
is not available but uint128_t is.  GCC before 5 are one of such
situatins.

See also https://rubyci.org/logs/rubyci.s3.amazonaws.com/opensuseleap/ruby-master/log/20191009T120004Z.log.html.gz







Changed numbered parameter prefix
2019-09-24T12:57:54+00:00

Nobuyoshi Nakada
nobu@ruby-lang.org

2019-09-03T15:07:50+00:00

ea68bb914a3c806a1c5188993b96791a76ab0849












add tests
2019-09-05T06:02:44+00:00

卜部昌平
shyouhei@ruby-lang.org

2019-09-05T06:02:07+00:00

436099ee0459ee51ceccb3eb343a5f281556bf61

Some coverage improvements.





Some coverage improvements.