From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9375 invoked by alias); 4 Jun 2002 09:20:42 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 9366 invoked from network); 4 Jun 2002 09:20:40 -0000 Received: from unknown (HELO nef.ens.fr) (129.199.96.32) by sources.redhat.com with SMTP; 4 Jun 2002 09:20:40 -0000 Received: from quatramaran.ens.fr (quatramaran.ens.fr [129.199.129.64]) by nef.ens.fr (8.10.1/1.01.28121999) with ESMTP id g549Kdp01800 for ; Tue, 4 Jun 2002 11:20:39 +0200 (CEST) Received: (from espie@localhost) by quatramaran.ens.fr (8.11.6/8.11.6) id g549KZP26811; Tue, 4 Jun 2002 11:20:35 +0200 Date: Tue, 04 Jun 2002 02:34:00 -0000 From: Marc Espie Message-Id: <200206040920.g549KZP26811@quatramaran.ens.fr> To: rth@redhat.com Subject: Re: Speeding up GC X-Newsgroups: ens.mailing-lists.egcs.general In-Reply-To: <20020603180553.A13829@redhat.com> References: Organization: Ecole Normale Superieure (quatramaran) Cc: gcc@gcc.gnu.org X-SW-Source: 2002-06/txt/msg00179.txt.bz2 In article <20020603180553.A13829@redhat.com> you write: > >A better way to do this is to actually compact the GC arena >and mark the pages read-only. If the objects are modified, >the SIGSEGV handler marks the page read-write again and flags >the page as having been modified. Isn't that a bit expensive ? getting through a SEGV and a signal-handler is not especially fast on most OSes.