Re: Changes to th new GC percentage feature

[Richard M. Stallman]

    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 think this is the clean fix.

The slowdown is surely insignificant.