This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: [Gc] Re: boehm-gc merge for GCC
- From: Matthias Klose <doko at ubuntu dot com>
- To: Bryce McKinlay <bmckinlay at gmail dot com>
- Cc: GCC Java <java at gcc dot gnu dot org>
- Date: Sat, 01 Dec 2012 21:50:05 +0100
- Subject: Re: [Gc] Re: boehm-gc merge for GCC
- References: <1353097280.505328435@f161.mail.ru> <50A67667.7020600@ubuntu.com> <CAF1jjLucRudE2a3gCZq6erkJKfs1nC+DicM+4f4moXJ5HPy9g@mail.gmail.com> <1353099257.140499471@f123.mail.ru> <CAF1jjLsA1nzLaJejMiAfzqZZ8btw37n0B3H7_qz-UrLvNQGqzA@mail.gmail.com> <50A6EE27.4000605@ubuntu.com> <50ABADE0.9000305@redhat.com> <50B385C5.6010004@ubuntu.com> <CALUNu-p3muXCwGV9sRSF550EvyM2=f0=mbEzDEhtf=BdhUJKMQ@mail.gmail.com> <CALUNu-pkdM8xXrJoCuJTW41zn0BiHntQLzC8=sLuHR2DbHVjbw@mail.gmail.com>
Am 26.11.2012 18:03, schrieb Bryce McKinlay:
> 2012 at 3:07 PM, Matthias Klose <doko@ubuntu.com> wrote:
>> So if the merge looks that problematic, maybe restart with trunk, maybe
>> check it in as bdwgc, and have toplevel configury to decide which one to use
>> until the update is stable, and then just drop the boehm-gc directory?
>
>
> I'm not sure it's worth making it configure-time switchable. I'd just put it
> on a branch, make sure it's working on the major platforms, and then merge
> to trunk once the GCC tree goes back in to stage 1.
ok. so I'll use
- branches/boehm for the import of the bdwgc branch
- branches/gcj/bdwgc-20121125-merge for the merge proposal
I'll start with what I currently have, and probably leave the libjava build on
the branch broken for some time. At least its stage1 material. Instead I'll
give the classpath merge priority, still considering it worth having for the 4.8
release.
Matthias