Re: GSoC 2016: proposal accepted!

Jörg & Daniel,
Last time I built clisp, it worked.
It is dog-slow, but I have never released clisp without first running
"make check" with DEBUG_GCSAFETY.
Briefly, CLISP GC moves memory, so any allocating function can trigger
GC and thus invalidates all objects.
Running at top-level
$ ./configure CC=g++ --with-debug build-debug-gxx-g
will configure CLISP in directory build-debug-gxx-g enabling various
run-time checks, and CC=g++ enables DEBUG_GCSAFETY (see makemake.in).
Thanks for mentioning this.
Sam


On Mon, May 2, 2016 at 1:35 PM,  <[email protected]> wrote:
> Daniel Jour wrote:
>>The testsuite is really impressive, though it doesn't help much when making
>>little changes. Thus I think about adding some tests that are closer to what
>>they tests.
>
> Sam, how to activate the C++ GC checker that makes use of the maygc annotations?
> Has it been used during later releases or is it bit rot?
> I believe it would be a valuable tool that helps checking low-level C code changes.
>
> If it still works, better not release anything without using it (I mean during
> pre-release tests, not in the released binary).
>
> OTOH, it's presumably not the first thing to try when initially diving through the code.
>
> Regards,
>         Jörg



-- 
Sam Steingold <http://sds.podval.org> <http://www.childpsy.net/>

------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
clisp-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-devel