[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gcl-devel] 2.6.2, random-tester progress

From: Vadim V. Zhytnikov
Subject: Re: [Gcl-devel] 2.6.2, random-tester progress
Date: Sun, 21 Mar 2004 18:59:51 +0300
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru-RU; rv:1.5) Gecko/20031006

Camm Maguire ?????:


Here is the summary of my understanding of the current state on

Remaining problems:

1) HEAD ansi-test failure "GO tag NIL not established" in routine
   setting a jmp with setjmp and branching to it with longjmp.

2) STABLE ansi-test failure in (classify-error (special-operator-p
   1)), which like all clcs error codes traps and branches to error
   handlers using longjmp.

3) Failure to build maxima with gcc-3.3.3

4) Failure to build maxima without removing (ignore-errors ....)

Gentlemen, all these appear to point to a setjmp/longjmp failure on
mingw, or at least gcl's use of such.  These can be heavily used by
the compiler at times, and its a bit embarrassing to ship such a
fragile situation.  We are sure to receive error reports about it for
some time, and it pretty much ensures that there must be a 2.6.3
later.  I will defer to the judgment of you three as you know the
windows situation far better than I -- we can either release what we
have, or fix this now if possible.  It should be a single fix as far
as I can tell.

As far as I can tell there are no issues on Linux, FreeBSD, MacOSX,
and Solaris.

If the three of you vote for 'release now', then Mike, please let me
know when your final installer bits are checked in and I'll make the
non-branch tag.  I've checked the memory management at the end of
maxpages, and it works correctly as far as I can see.  One needs
'256*1024' maxpages to run Paul's tester with 10,000/8.  At this size,
my test has been running now for > 24 hours, and I feel we have a good
shot at reaching the clisp 'bogey' of ~ 45k tests.  Am curious to know
how much memory clisp needs to compile these forms for this long.

Take care,

If you think that all these Windows problems probably due
to the same error then we can try to fix it.
I'm inclined to believe your intuition.  The only bad thing about me
personally is what with high probability I'll be able to do any debugging only to the end of coming week - maybe next weekend.

     Vadim V. Zhytnikov


reply via email to

[Prev in Thread] Current Thread [Next in Thread]