Frank Heckenbach wrote:
Backtraces are at the bottom of this messages. It seems that Mac OS X doesn't like Mr. "R" ....
The read tests are quite heavy on stack usage. If you can increase the system limit (ulimit etc.), you might want try that. But I'm changing them now to reduce stack usage, so in the next GPC version, they might work (unless it's actually another bug).
Increasing the stacksize eliminates most test failures, including the gpc internal errors !!
[G4:~/gnu/testgpc/test] adriaan% limit stacksize 2048 [G4:~/gnu/testgpc/test] adriaan% make
[results included as attachement]
# of GPC tests 2856 # of GPC tests passed 2828 # of GPC tests skipped 18 # of GPC tests failed 10
This surpasses all my expectations. We are near to opening up a bottle of champagne !
Leaves the nonlocal goto bug ...
9 out of 10 failed tests, if I am right - fjf558m.pas, fjf558n.pas, fproc.pas, goto4.pas, goto5.pas, math.pas, nlgpp.pas, nlgpp2.pas and nonlocgoto.pas.
This reminds me of UCSD Pascal for the Apple II. It had a "Goto statements options" (G+,G-) aimed at students "to keep novice programmers from using the GOTO statement ..." Shouldn't we keep Macintosh programmers out of it also ?
Nevertheless, I will search the web for patches to the gcc powerpc back-end.
The remaining failed test is systemtest.pas: Error in HeapError #2
I didn't study GetMem in detail, but why not allocate 2147483391 bytes of virtual memory ?
Regards,
Adriaan van Os