This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Speeding up GC
In article <20020604.072448.55836404.davem@redhat.com> you write:
>I think messing around with dirty bits and OS interfaces to set/reset
>them is absolutely the wrong path to go down. This is going to make
>GC much more complex from a per-host standpoint. I also, for similar
>reasons, think the SIGSEGV+mprotect idea is bad too. I can guarentee
>you we will need to disable this on half the platforms that have a
>working mmap() because of either a) OS bugs in providing the correct
>fault address to the SIGSEGV handler b) us not being able to figure
>out how to make it work on a particular platform.
>
Thank you ! you formulated very well what I was thinking, and was not
able to pinpoint precisely.
Actually, I can pinpoint it partly: going down such a path would
1/ make gcc very much linux-dependent. Or at least, turn it into trash on
platforms without a `fast/non-buggy' SEGV+mprotect hack.
2/ help hide other inefficiencies in the compiler... and since the majority
of gcc users are i*86-*-linux*, well, you can guess the rest.