Re: lang/clisp vs. gcc?

[Joerg Sonnenberger <joerg%bec.de@localhost>]

On Sat, Jan 05, 2019 at 06:27:04PM +0100, Havard Eidnes wrote:
> I vaguely seem to recall that there's a chance this is the result of
> gcc being too clever by half and doing weird things with calloc() /
> malloc() optimization?  I have clisp suspected of (trying to?) define
> one of these or both itself, leading to this rather tight CPU-bound
> loop.

-fno-builtin-calloc for gmalloc.c or so.

Joerg