Frank Heckenbach wrote:
Which command exactly did you run, and from which directory? If from the build directory, what does <build>/gcc/p/test/Makefile contain? I suppose, `srcdir' is not set correctly there (i.e., to `.' instead of the source directory). If so, there might be a problem with the sed substitution (gcc/p/Make-lang.in:1022) that creates this Makefile -- either with the regex or the sed invocation or pwd or something else ... I don't see a problem now, but if you play around with it, you might be able to find it out. (You'll have to remove <build>/gcc/p/test/Makefile so it's rebuilt when you change something in Make-lang.in.)
I will try to find out and report about it. For now, I ran the testsuite with the Makefile from the previous alpha version.
fjf558m.pas Bus error non-local goto bug (gcc) fjf558n.pas Bus error non-local goto bug (gcc) fjf558o.pas Bus error non-local goto bug (gcc) fjf558p.pas Bus error non-local goto bug (gcc) fjf582.pas Segmentation fault stack overflow (solved with "limit stacksize 2048") fjf664.pas Segmentation fault stack overflow (solved with "limit stacksize 2048") fproc.pas Segmentation fault non-local goto bug (gcc) goto5.pas Bus error non-local goto bug (gcc) nlgpp.pas Bus error non-local goto bug (gcc) nlgpp2.pas Bus error non-local goto bug (gcc) systemtest.pas malloc error malloc bug in OS X
It's an interesting option to add -fstack-check to the test suite:
./read2.inc: In procedure `R': In file included from ./readg1.pas:9: ./read2.inc:203: warning: frame size too large for reliable stack checking ./read2.inc:203: warning: try reducing the number of local variables failed
Could you please try that again after the release of the next GPC alpha?
I did and the result is included as an attachement to this email.
The gpc-20021128 test suite produces other strange results:
TEST adam2.pas: gpc1: warnings being treated as errors adam2v.pas:12: warning: varying case of `aLimit' adam2v.pas:7: warning: other case: `ALimit' adam2v.pas: In constructor `MList.Init': adam2v.pas:14: warning: varying case of `ALimit' adam2v.pas:12: warning: other case: `aLimit' ..... (etcetera)
That's not strange. That's the new warning I've suggested here recently (and implemented now). :-)
I apologize. I associated "case" with the case statement rather than with uppercase and lowercase.
Regards,
Adriaan van Os