Parrot 7.0.0 "Crimson Shining Parrot" | parrot.org/ | Log: irclog.perlgeek.de/parrot | #parrotsketch meeting Fridays 13:30 UTC
Set by moderator on 21 January 2015.
00:33 lauleon joined 01:52 lauleon joined 02:06 lauleon joined 03:18 Psyche^ joined 03:27 kid51 joined 06:41 rurban joined
rurban Ah, GC regression --optimized in rpa's 07:40
I think this requires a 7.0.1 release 07:51
hmm, the wrong attribute was added with 3.6.0, but starts being fatal with 7.0 07:57
08:11 FROGGS joined
dalek rrot/smoke-me/thread-lock-gh1187: e2648b6 | rurban++ | / (2 files):
[pmc] rpa: fix custom_mark_destroy confusion

custom_mark_destroy is only needed in the init method, which is fpa.set_integer_native. optimize PObj_custom_mark_destroy_SETALL to use only one setter call.
09:23
rrot/smoke-me/thread-lock-gh1187: 4d173db | rurban++ | / (2 files):
[atomic] cannot mix PARROT_EXPORT + PARROT_INLINE

remove the INLINE
rrot/smoke-me/thread-lock-gh1187: 966da74 | rurban++ | / (3 files):
[GC] fix GC segfault with --optimize

A wrong PARROT_CANNOT_RETURN_NULL in Parrot_pf_get_current_code_segment
  (unchecked return of inter->code, which can be null) causes GC segfaults
when inter->code == NULL.
Fixes GH #1186. This wrong PARROT_CANNOT_RETURN_NULL was added with 3.6.0 in 7dc0e2276d3612afd at Wed Jun 29 20:52:24 2011 but started being fatal after the new packfile refactor with 7.0, when the cc optimizer started optimizing away the bc != NULL check in mark_code_segment()
rrot/smoke-me/thread-lock-gh1187: fe3b311 | rurban++ | src/gc/mark_sweep.c:
[GC] optimize away a Parrot_pf_get_current_code_segment call

This was the call with the wrong CANNOT_RETURN_NULL attribute, causing GH #1186. We only need inter->code, and it can be const. The const_table also
rrot/smoke-me/thread-lock-gh1187: bd48208 | rurban++ | src/gc/gc_gms.c:
[threads] fix deadlock in gc_gms_mark_and_sweep

move the lock downwards to the guard. Fixes GH #1187
rrot/smoke-me/thread-lock-gh1187: 2ef09ef | rurban++ | src/gc/gc_gms.c:
threads: refactor thread locks in the GC

Simplify GC locks to new macros:
  - THREAD_COND_{UN,}LOCK only if locked/lockable (with the self->locked guard)
  - THREAD_{UN,}LOCK unconditionally (race free).
rrot: fbc7817 | rurban++ | include/parrot/atomic/gcc_x86.h:
[codingstd] include/parrot/atomic/gcc_x86.h c_indent.t
09:43
rrot: aae3b13 | rurban++ | / (2 files):
[atomic] cannot mix PARROT_EXPORT + PARROT_INLINE

remove the INLINE
rrot: 606d9fd | rurban++ | / (2 files):
[pmc] rpa: fix custom_mark_destroy confusion

custom_mark_destroy is only needed in the init method, which is fpa.set_integer_native. optimize PObj_custom_mark_destroy_SETALL to use only one setter call.
rrot: bf01f77 | rurban++ | / (3 files):
[GC] fix GC segfault with --optimize

A wrong PARROT_CANNOT_RETURN_NULL in Parrot_pf_get_current_code_segment
  (unchecked return of inter->code, which can be null) causes GC segfaults
when inter->code == NULL.
Fixes GH #1186. This wrong PARROT_CANNOT_RETURN_NULL was added with 3.6.0 in 7dc0e2276d3612afd at Wed Jun 29 20:52:24 2011 but started being fatal after the new packfile refactor with 7.0, when the cc optimizer started optimizing away the bc != NULL check in mark_code_segment()
rrot: c73b9b8 | rurban++ | src/gc/mark_sweep.c:
[GC] optimize away a Parrot_pf_get_current_code_segment call

This was the call with the wrong CANNOT_RETURN_NULL attribute, causing GH #1186. We only need inter->code, and it can be const. The const_table also
rrot: 05dc43f | rurban++ | src/gc/gc_gms.c:
[threads] fix deadlock in gc_gms_mark_and_sweep

move the lock downwards to the guard. Fixes GH #1187
09:49 travis-ci joined
travis-ci parrot/parrot#1507 (smoke-me/thread-lock-gh1187 - 2ef09ef : Reini Urban): The build has errored. 09:49
Change view : github.com/parrot/parrot/compare/e...f09ef408c9
Build details : travis-ci.org/parrot/parrot/builds/47893473
09:49 travis-ci left 10:01 travis-ci joined
travis-ci parrot/parrot#1508 (master - 05dc43f : Reini Urban): The build passed. 10:01
Change view : github.com/parrot/parrot/compare/3...dc43fc8b4c
Build details : travis-ci.org/parrot/parrot/builds/47895149
10:01 travis-ci left
dalek rrot/smoke-me/7.0.1: 1bfb43c | rurban++ | docs/project/release_manager_guide.pod:
[docs] cover 7.3 in release_manager_guide
10:29
rrot/smoke-me/7.0.1: ba5fd2f | rurban++ | docs/project/release_manager_guide.pod:
[docs] minor release_manager_guide improvement
rrot/smoke-me/7.0.1: 0006e12 | rurban++ | / (2 files):
[pmc] rpa: fix custom_mark_destroy confusion

custom_mark_destroy is only needed in the init method, which is fpa.set_integer_native. optimize PObj_custom_mark_destroy_SETALL to use only one setter call.
rrot/smoke-me/7.0.1: 56c7036 | rurban++ | / (3 files):
[GC] fix GC segfault with --optimize

A wrong PARROT_CANNOT_RETURN_NULL in Parrot_pf_get_current_code_segment
  (unchecked return of inter->code, which can be null) causes GC segfaults
when inter->code == NULL.
Fixes GH #1186. This wrong PARROT_CANNOT_RETURN_NULL was added with 3.6.0 in 7dc0e2276d3612afd at Wed Jun 29 20:52:24 2011 but started being fatal after the new packfile refactor with 7.0, when the cc optimizer started optimizing away the bc != NULL check in mark_code_segment()
rrot/smoke-me/7.0.1: f14a5a1 | rurban++ | src/gc/mark_sweep.c:
[GC] optimize away a Parrot_pf_get_current_code_segment call

This was the call with the wrong CANNOT_RETURN_NULL attribute, causing GH #1186. We only need inter->code, and it can be const. The const_table also
rrot/smoke-me/7.0.1: 5069da4 | rurban++ | src/gc/gc_gms.c:
[threads] fix deadlock in gc_gms_mark_and_sweep

move the lock downwards to the guard. Fixes GH #1187
rrot/smoke-me/7.0.1: 9b15f24 | rurban++ | / (21 files):
7.0.1 hotfix release

Todo the 2nd t/stress/threads.t test, caused by stringbuilder gc, probably #1123.
rrot/smoke-me/7.0.1: 1bfb43c | rurban++ | docs/project/release_manager_guide.pod:
[docs] cover 7.3 in release_manager_guide
10:33
rrot/smoke-me/7.0.1: ba5fd2f | rurban++ | docs/project/release_manager_guide.pod:
[docs] minor release_manager_guide improvement
rrot/smoke-me/7.0.1: 0006e12 | rurban++ | / (2 files):
[pmc] rpa: fix custom_mark_destroy confusion

custom_mark_destroy is only needed in the init method, which is fpa.set_integer_native. optimize PObj_custom_mark_destroy_SETALL to use only one setter call.
rrot/smoke-me/7.0.1: 56c7036 | rurban++ | / (3 files):
[GC] fix GC segfault with --optimize

A wrong PARROT_CANNOT_RETURN_NULL in Parrot_pf_get_current_code_segment
  (unchecked return of inter->code, which can be null) causes GC segfaults
when inter->code == NULL.
Fixes GH #1186. This wrong PARROT_CANNOT_RETURN_NULL was added with 3.6.0 in 7dc0e2276d3612afd at Wed Jun 29 20:52:24 2011 but started being fatal after the new packfile refactor with 7.0, when the cc optimizer started optimizing away the bc != NULL check in mark_code_segment()
rrot/smoke-me/7.0.1: f14a5a1 | rurban++ | src/gc/mark_sweep.c:
[GC] optimize away a Parrot_pf_get_current_code_segment call

This was the call with the wrong CANNOT_RETURN_NULL attribute, causing GH #1186. We only need inter->code, and it can be const. The const_table also
rrot/smoke-me/7.0.1: 5069da4 | rurban++ | src/gc/gc_gms.c:
[threads] fix deadlock in gc_gms_mark_and_sweep

move the lock downwards to the guard. Fixes GH #1187
rrot/smoke-me/7.0.1: e9ff596 | rurban++ | / (21 files):
7.0.1 hotfix release

Todo the 2nd t/stress/threads.t test, caused by stringbuilder gc, probably #1123.
10:34 travis-ci joined
travis-ci parrot/parrot#1509 (smoke-me/7.0.1 - 9b15f24 : Reini Urban): The build was canceled. 10:34
Change view : github.com/parrot/parrot/compare/1...15f2474e7b
Build details : travis-ci.org/parrot/parrot/builds/47898708
10:34 travis-ci left 10:47 travis-ci joined
travis-ci parrot/parrot#1510 (smoke-me/7.0.1 - e9ff596 : Reini Urban): The build passed. 10:47
Change view : github.com/parrot/parrot/compare/1...ff596733bf
Build details : travis-ci.org/parrot/parrot/builds/47898969
10:47 travis-ci left 12:27 rurban joined 12:50 kid51 joined 13:52 rurban1 joined 16:02 rurban joined 16:09 rurban1 joined 17:26 Hunger joined 18:32 FROGGS joined 18:33 FROGGS_ joined 22:44 rurban joined