Here's another data-point, for Linux/x86: with a fresh check-out, parrot is passing all of its tests, but most of the imcc tests are failing. Specifically, I get:
Failed Test Stat Wstat Total Fail Failed List of Failed ------------------------------------------------------------------ t/syn/clash.t 5 1280 5 5 100.00% 1-5 t/syn/const.t 3 768 3 3 100.00% 1-3 t/syn/eval.t 2 512 3 2 66.67% 1-2 t/syn/labels.t 3 768 3 3 100.00% 1-3 t/syn/namespace.t 3 768 3 3 100.00% 1-3 t/syn/scope.t 3 768 3 3 100.00% 1-3 1 subtest skipped. Failed 6/9 test scripts, 33.33% okay. 19/24 subtests failed, 20.83% okay. Closer examination suggests that all of these tests are failing because imcc is sgefaulting; a representative backtrace is: Program received signal SIGSEGV, Segmentation fault. 0x080dfb0a in pobject_lives () (gdb) bt #0 0x080dfb0a in pobject_lives () #1 0x080ec252 in Parrot_NCI_mark () #2 0x080dfe94 in trace_active_PMCs () #3 0x080e03ac in Parrot_do_dod_run () #4 0x080e4cdd in more_traceable_objects () #5 0x080e4d7c in get_free_object () #6 0x080df260 in get_free_buffer () #7 0x080df61a in new_bufferlike_header () #8 0x080b60e3 in list_new () #9 0x080e51ff in Parrot_Array_init () #10 0x080b76ae in setup_argv () #11 0x080b7834 in Parrot_runcode () #12 0x0805693a in main () ...which looks to be related to the problem people are encountering on the other platforms. Hope this is useful, Simon
