User Story

Attachments

(1 attachment)

The followin tests segfault on ppc64 non-interp:
ecma3/Boolean/e15_6_4_3_2.abc
ecma3/Boolean/e15_6_4_3_3.abc
ecma3/Expressions/e11_2_1_2.abc
ecma3/Expressions/e11_2_1_5.abc
ecma3/ObjectObjects/e15_2_2_1_rt.abc
ecma3/ObjectObjects/e15_2_1_1_rt.abc
ecma3/TypeConversion/e9_9_1_rt.abc
Result:
Segmentation Fault
exit code: -11
They must be compiled with -AS3. To do this, move the ecma3/dir.asc_args file to somewhere else temporarily then run the tests using -f.
I can also provide the .abc files if needed.

These tests are currently passing with the exact-gc patch queue on mac64-ppc. Lars suggested having Edwin take a look at this issue and I will be sending machine/source information to Edwin offlien.
Lars: "That suggests that the bug shows up in part because of heap dynamics, and since those are changing with exact tracing the bug might have hidden itself again. Might want to ping Edwin about looking for the bug sooner rather than later."

After looking at this some more, it is not true that all of the tests are now passing. They no longer crash the VM, but the vm is now not producing the correct results for all of the tests:
ecma3/Expressions/e11_2_1_2.abc : false.valueOf() = FAILED! expected: false
ecma3/Expressions/e11_2_1_2.abc : false.toString() = true FAILED! expected: false
ecma3/Expressions/e11_2_1_5.abc : false.valueOf() = FAILED! expected: false
ecma3/Expressions/e11_2_1_5.abc : false.toString() = true FAILED! expected: false
ecma3/ObjectObjects/e15_2_1_1_rt.abc : Object(false).valueOf() = FAILED! expected: false
I have tried to isolate the failing code but it does not appear to fail in the same manner when the code is isolated.

I haven't had any time to look at this, and probably won't for a while. How important is it? (its targeted for Serrano, but has no priority set... uh oh). The looming question is who will be maintaining PPC64.
Do we have good evidence this is PPC64 only and not PPC32?