20 Jan
2003
20 Jan
'03
2:56 a.m.
Adriaan van Os wrote:
Frank Heckenbach wrote:
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).
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?
Frank
--
Frank Heckenbach, frank@g-n-u.de, http://fjf.gnu.de/, 7977168E
GPC To-Do list, latest features, fixed bugs:
http://www.gnu-pascal.de/todo.html
GPC download signing key: 51FF C1F0 1A77 C6C2 4482 4DDC 117A 9773 7F88 1707