From: Matthias Klose <doko@ubuntu.com>
To: Bryce McKinlay <bmckinlay@gmail.com>
Cc: GCC Java <java@gcc.gnu.org>
Subject: Re: [Gc] Re: boehm-gc merge for GCC
Date: Sat, 01 Dec 2012 20:50:00 -0000 [thread overview]
Message-ID: <50BA6D7D.8020106@ubuntu.com> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2012-12-01 20:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1353097280.505328435@f161.mail.ru>
[not found] ` <50A67667.7020600@ubuntu.com>
[not found] ` <CAF1jjLucRudE2a3gCZq6erkJKfs1nC+DicM+4f4moXJ5HPy9g@mail.gmail.com>
[not found] ` <1353099257.140499471@f123.mail.ru>
[not found] ` <CAF1jjLsA1nzLaJejMiAfzqZZ8btw37n0B3H7_qz-UrLvNQGqzA@mail.gmail.com>
[not found] ` <50A6EE27.4000605@ubuntu.com>
[not found] ` <50ABADE0.9000305@redhat.com>
[not found] ` <50B385C5.6010004@ubuntu.com>
[not found] ` <CALUNu-p3muXCwGV9sRSF550EvyM2=f0=mbEzDEhtf=BdhUJKMQ@mail.gmail.com>
2012-11-26 17:03 ` Bryce McKinlay
2012-11-26 17:50 ` Andrew Haley
2012-11-27 1:09 ` Boehm, Hans
2012-12-01 20:50 ` Matthias Klose [this message]
2012-12-02 2:51 ` Matthias Klose
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=50BA6D7D.8020106@ubuntu.com \
--to=doko@ubuntu.com \
--cc=bmckinlay@gmail.com \
--cc=java@gcc.gnu.org \
/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).