Frank Heckenbach wrote:
Adriaan van Os wrote:
Frank Heckenbach wrote:
I've uploaded a new alpha to http://www.gnu-pascal.de/alpha/
It builds on Mac OS X. Testsuite results are as expected (known back-end issues)
That's only the nonlocal goto bug (if you apply the backend patches), or anything else?
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
I assume, the malloc bug will get fixed in some future release of Mac OS X.
I've had the idea that this can maybe be worked-around by using longjmp (as is done for nonlocal gotos into the main program which work AFAIR). I haven't dealt with label internals much, so I don't know how difficult this will be, but I may look into it when I get to it ...
Are non-local goto's used in C ? If not, do the gcc guys accept Pascal or RTL programs in bug reports ? Is there something like an RTL interpreter, for debugging and to isolate back-end from front-end bugs ?
except that fjf581f.pas writes 'OO' to stdout.
TEST fjf781f.pas: OO
Hmm, the test program may be wrong. Try this one.
It now passes the testsuite.
Regards,
Adriaan van Os