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. 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.
