From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4888 invoked by alias); 18 Jun 2009 23:39:11 -0000 Received: (qmail 4880 invoked by uid 22791); 18 Jun 2009 23:39:11 -0000 X-SWARE-Spam-Status: No, hits=-1.1 required=5.0 tests=AWL,BAYES_00,NO_DNS_FOR_FROM X-Spam-Check-By: sourceware.org Received: from e32.co.us.ibm.com (HELO e32.co.us.ibm.com) (32.97.110.150) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 18 Jun 2009 23:39:03 +0000 Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106]) by e32.co.us.ibm.com (8.13.1/8.13.1) with ESMTP id n5INZBc0013638 for ; Thu, 18 Jun 2009 17:35:11 -0600 Received: from d03av03.boulder.ibm.com (d03av03.boulder.ibm.com [9.17.195.169]) by d03relay04.boulder.ibm.com (8.13.8/8.13.8/NCO v9.2) with ESMTP id n5INcxt5219082 for ; Thu, 18 Jun 2009 17:38:59 -0600 Received: from d03av03.boulder.ibm.com (loopback [127.0.0.1]) by d03av03.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id n5INcx1a006267 for ; Thu, 18 Jun 2009 17:38:59 -0600 Received: from hungry-tiger.westford.ibm.com (hungry-tiger.westford.ibm.com [9.33.20.67]) by d03av03.boulder.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id n5INcwdD006264; Thu, 18 Jun 2009 17:38:59 -0600 Received: by hungry-tiger.westford.ibm.com (Postfix, from userid 500) id ABDB557BE3; Thu, 18 Jun 2009 19:38:58 -0400 (EDT) Date: Thu, 18 Jun 2009 23:39:00 -0000 From: Michael Meissner To: NightStrike Cc: gcc@gcc.gnu.org Subject: Re: GCC and boehm-gc Message-ID: <20090618233858.GA7014@hungry-tiger.westford.ibm.com> Mail-Followup-To: Michael Meissner , NightStrike , gcc@gcc.gnu.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i X-IsSubscribed: yes Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2009-06/txt/msg00455.txt.bz2 On Thu, Jun 18, 2009 at 12:10:53PM -0400, NightStrike wrote: > Given the recent issues with libffi being so drastically out of synch > with upstream, I was curious about boehm-gc and how that is handled. > In getting gcj to work on Win64, the next step is boehm-gc now that > libffi works just fine. However, the garbage collector is in terrible > shape and will need a bit of work. Do we send those fixes here to > GCC, or to some other project? Who handles it? How is the synching > done compared to other external projects? I have the following patch that is waiting for approval. I sent mail to the list Tom Tromey mentioned in the followup, but I haven't seen a reply yet. http://gcc.gnu.org/ml/gcc-patches/2009-06/msg01094.html -- Michael Meissner, IBM 4 Technology Place Drive, MS 2203A, Westford, MA, 01886, USA meissner@linux.vnet.ibm.com