| commit | 2d525b793f1b0fd2b6f66881310bec8684bceffe | |
| author | Tom Tromey <tromey@redhat.com> | |
| Wed, 15 Aug 2012 19:01:36 +0000 (15 13:01 -0600) | ||
| committer | Tom Tromey <tromey@redhat.com> | |
| Wed, 15 Aug 2012 19:01:36 +0000 (15 13:01 -0600) | ||
| tree | 932fb8b75974ac4c16ecfc5bc216fe362b0a4d27 | treesnapshot (tar.gz zip) |
| parent | 68b32482437e05f0994c4dd0ab5b0c27d39f0f6d | commitdiff |
This parameterizes the GC a bit to make it thread-ready.
The basic idea is that whenever a thread "exits lisp" -- that is,
releases the global lock in favor of another thread -- it must save
its stack boundaries in the thread object. This way the boundaries
are always available for marking. This is the purpose of
flush_stack_call_func.
I haven't tested this under all the possible GC configurations.
There is a new FIXME in a spot that i didn't convert.
Arguably all_threads should go in the previous patch.
The basic idea is that whenever a thread "exits lisp" -- that is,
releases the global lock in favor of another thread -- it must save
its stack boundaries in the thread object. This way the boundaries
are always available for marking. This is the purpose of
flush_stack_call_func.
I haven't tested this under all the possible GC configurations.
There is a new FIXME in a spot that i didn't convert.
Arguably all_threads should go in the previous patch.