From: Andrew Haley <aph@redhat.com>
To: java@gcc.gnu.org
Subject: Re: GC leaks debugging
Date: Wed, 13 Apr 2011 14:27:00 -0000 [thread overview]
Message-ID: <4DA5B2AF.9010009@redhat.com> (raw)
In-Reply-To: <BANLkTimRd_BzxgrxLh1xLMn6=PB4asUUNw@mail.gmail.com>
On 04/13/2011 01:11 PM, Bryce McKinlay wrote:
> On Wed, Apr 13, 2011 at 9:11 AM, Andrew Haley <aph@redhat.com> wrote:
>> On 12/04/11 19:42, Erik Groeneveld wrote:
>
>>> Meanwhile, I'd like to pursue a better solution - less of a hack. Any
>>> interest in helping out?
>>
>> Before you go any further, it's worth remembering that you're using an
>> old version of the GC. I've been told that "Of course, [the new gc]
>> will require modification of boehm.cc in GCJ" but not why.
>>
>> It looks like you're making progress, but I urge you to move to the
>> new gc or your time may be wasted on the old one.
>
> Now would certainly be a good time to work on a boehm-gc import, with
> GCC in stage 1.
>
> Note that Kai Tietz has recently expressed interest in working on this, too:
> http://gcc.gnu.org/ml/gcc/2011-04/msg00006.html
>
> "svn import" and "svn merge" are your friends here. The unmodified
> upstream sources from the last time we merged are tagged as GC_6_6.
> IIRC, the local modifications at that time were fairly minimal, mostly
> just configure changes. If you import the current sources with a
> similar tag, it'll make it easy to get a diff of the GCC tree's
> current divergences, which can then be submitted upstream if
> appropriate.
I think we're a bit further down the road than that, judging by the
traffic on the gc list. Ivan Madanski said
> I've reviewed the patches from gcc/boem-gc. The following ones I'm
> unable to process (and some at GCC side should have a look at, may
> be the original patch authors could adopt their ones for GC v7+):
>
> bgc-167681 - darwin-specific (probably this one no longer needed for v7+);
> bgc-171516 - testsuite-specific;
> bgc-144045 bgc-150269 bgc-151013 bgc-151627 bgc-166028 - scripts-specific ones;
> bgc-114869, bgc-124081 - specific to thread suspension.
So these are the only patches that require special handling by someone
on the gcc side.
Andrew.
next prev parent reply other threads:[~2011-04-13 14:27 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-01 8:39 Erik Groeneveld
2011-04-01 8:45 ` Andrew Haley
2011-04-01 9:03 ` Erik Groeneveld
2011-04-01 9:34 ` Andrew Haley
2011-04-02 0:27 ` Boehm, Hans
2011-04-02 9:39 ` Erik Groeneveld
2011-04-03 17:15 ` Erik Groeneveld
2011-04-03 18:00 ` Erik Groeneveld
2011-04-04 8:13 ` Andrew Haley
2011-04-04 8:53 ` Erik Groeneveld
2011-04-04 9:48 ` Andrew Haley
2011-04-05 4:44 ` Boehm, Hans
2011-04-05 8:58 ` Andrew Haley
2011-04-05 6:50 ` Erik Groeneveld
2011-04-05 9:02 ` Andrew Haley
2011-04-05 12:02 ` Erik Groeneveld
2011-04-05 12:55 ` Andrew Haley
2011-04-06 14:30 ` Erik Groeneveld
2011-04-06 18:33 ` Andrew Haley
2011-04-06 18:39 ` David Daney
2011-04-07 17:43 ` Erik Groeneveld
2011-04-08 8:12 ` Erik Groeneveld
2011-04-08 13:56 ` Andrew Haley
2011-04-08 15:35 ` David Daney
2011-04-08 15:53 ` Erik Groeneveld
2011-04-08 15:57 ` Andrew Haley
2011-04-08 15:48 ` Erik Groeneveld
2011-04-09 1:17 ` Boehm, Hans
2011-04-09 8:47 ` Andrew Haley
2011-04-09 10:56 ` Erik Groeneveld
2011-04-10 11:03 ` Erik Groeneveld
2011-04-12 18:43 ` Erik Groeneveld
2011-04-13 8:11 ` Andrew Haley
2011-04-13 12:11 ` Bryce McKinlay
2011-04-13 14:27 ` Andrew Haley [this message]
2011-04-14 8:36 ` Erik Groeneveld
2011-04-14 8:43 ` Andrew Haley
2011-04-14 10:02 ` Erik Groeneveld
2011-04-14 10:50 ` Andrew Haley
2011-04-15 7:32 ` Erik J Groeneveld
2011-04-01 17:41 ` David Daney
2011-04-02 16:21 ` Erik Groeneveld
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DA5B2AF.9010009@redhat.com \
--to=aph@redhat.com \
--cc=java@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).