From: David Daney <ddaney@caviumnetworks.com>
To: NightStrike <nightstrike@gmail.com>
Cc: gcc@gcc.gnu.org, hans.boehm@hp.com
Subject: Re: GCC and boehm-gc
Date: Thu, 18 Jun 2009 16:27:00 -0000 [thread overview]
Message-ID: <4A3A6AD8.70207@caviumnetworks.com> (raw)
In-Reply-To: <b609cb3b0906180910n48417dbbkf31e014b30c38daf@mail.gmail.com>
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).
David Daney
next prev parent reply other threads:[~2009-06-18 16:27 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 [this message]
2009-06-18 16:46 ` NightStrike
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=4A3A6AD8.70207@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=gcc@gcc.gnu.org \
--cc=hans.boehm@hp.com \
--cc=nightstrike@gmail.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).