NightStrike wrote:
On Thu, Jun 18, 2009 at 12:58 PM, Andrew Haley<a...@redhat.com> wrote:
NightStrike wrote:
On Thu, Jun 18, 2009 at 12:27 PM, David Daney<dda...@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.
No, it's not. The problem with libffi is that it was updated in gcc and
upstream; that is much less of a problem with boehm-gc.
That's what David just described -- that there are both GCC local
changes and upstream changes.
Regardless, someone with the knowledge and background needs to do this merge.
Or someone willing to acquire such knowledge and background by
attempting to do the merge and presenting the results of their efforts
for review.
David Daney
