Re: Changes to th new GC percentage feature

[Stefan Monnier]

>     what exactly is it trying to do?  The only changes I can notice are:
>     - the bytecode interpreter and the eval and funcall functions now
>       check two values rather than one, thus being slower.
>     - read_char tests gc_cons_threshold.

> There is code that temporarily changes gc_cons_threshold to prevent
> GC from occurring.  It was broken and caused an infinite recursion.

I thought I had carefully updated it to change
gc_cons_combined_threshold instead.

> I think this is the clean fix.

OK.

> The slowdown is surely insignificant.

I'd expect it to be measurable since it's executed at the very least least
once per iteration of any loop.


        Stefan