public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: NightStrike <nightstrike@gmail.com>
To: David Daney <ddaney@caviumnetworks.com>
Cc: gcc@gcc.gnu.org, hans.boehm@hp.com
Subject: Re: GCC and boehm-gc
Date: Thu, 18 Jun 2009 16:46:00 -0000	[thread overview]
Message-ID: <b609cb3b0906180945o43b3259ata235effb8ac61b61@mail.gmail.com> (raw)
In-Reply-To: <4A3A6AD8.70207@caviumnetworks.com>

On Thu, Jun 18, 2009 at 12:27 PM, David Daney<ddaney@caviumnetworks.com> wrote:
> 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?
>>
>
> Your analysis of the situation is essentially correct.
>
> Hans (now CCed) is good about merging changes to the upstream sources,
> but we haven't updated GCC/libgcj's copy in quite some time.  A
> properly motivated person would have to import a newer version of the
> GC checking that all GCC local changes were either already merged, or
> if not port them to the new GC (those that are not upstream should
> then be evaluated to see if they should be).

So it seems that boehm-gc is in the exact state as libffi.

This is yet another example of why we shouldn't duplicate sources...

Hans, would you be willing to bring boehm-gc up to speed so that we
can start getting it to work for Win64?  Without this, we obviously
cannot add gcj to our list of supported compilers.

  reply	other threads:[~2009-06-18 16:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-18 16:11 NightStrike
2009-06-18 16:27 ` David Daney
2009-06-18 16:46   ` NightStrike [this message]
2009-06-18 16:59     ` Andrew Haley
2009-06-18 17:08       ` David Daney
2009-06-18 17:09       ` NightStrike
2009-06-18 17:17         ` David Daney
2009-06-18 21:16     ` Hans Boehm
2009-06-18 21:41       ` NightStrike
2009-06-18 18:03 ` Andrew Haley
2009-06-18 18:20   ` NightStrike
2009-06-18 19:19     ` Andrew Haley
2009-06-18 23:39 ` Michael Meissner

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=b609cb3b0906180945o43b3259ata235effb8ac61b61@mail.gmail.com \
    --to=nightstrike@gmail.com \
    --cc=ddaney@caviumnetworks.com \
    --cc=gcc@gcc.gnu.org \
    --cc=hans.boehm@hp.com \
    /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).