From: Andrew Haley <aph@redhat.com>
To: David Daney <ddaney.cavm@gmail.com>
Cc: Matthias Klose <doko@ubuntu.com>, GCJ-patches <java-patches@gcc.gnu.org>
Subject: Re: classpath merge for gcc-4.8?
Date: Wed, 07 Nov 2012 10:58:00 -0000 [thread overview]
Message-ID: <509A3EAD.6060906@redhat.com> (raw)
In-Reply-To: <509987B5.2050904@gmail.com>
On 11/06/12 21:57, David Daney wrote:
> On 11/06/2012 12:38 PM, Matthias Klose wrote:
>> classpath wasn't merged for the gcc-4.7 release, is anybody working on a
>> merge for gcc-4.8? stage1 is finished now, however I think this should
>> still be possible to do for 4.8.
>>
>> as a related topic, should an update of boehm-gc be addressed too?
>>
>
> I am not a maintainer, but I would say yes to both questions.
>
> Really the importance of GCJ/libgcj relative to GCC is lower than it
> used to be, so I doubt that doing this in a non-stage1 stage really
> matters that much.
Perhaps not, but now is an excellent time to do it.
Andrew.
next prev parent reply other threads:[~2012-11-07 10:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-06 20:38 Matthias Klose
2012-11-06 21:57 ` David Daney
2012-11-07 10:58 ` Andrew Haley [this message]
2012-11-07 17:19 ` Andrew Hughes
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=509A3EAD.6060906@redhat.com \
--to=aph@redhat.com \
--cc=ddaney.cavm@gmail.com \
--cc=doko@ubuntu.com \
--cc=java-patches@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).